mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: xen-devel@lists.xenproject.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Subject: Re: [PATCH] xen: don't require virtio with grants for non-PV guests
Date: Wed, 15 Jun 2022 11:32:40 +0200	[thread overview]
Message-ID: <a063368a-022a-c294-5a19-da1b80c45461@suse.com> (raw)
In-Reply-To: <20220615092519.5677clabobheziet@vireshk-i7>


[-- Attachment #1.1.1: Type: text/plain, Size: 2568 bytes --]

On 15.06.22 11:25, Viresh Kumar wrote:
> On 15-06-22, 10:48, Juergen Gross wrote:
>> Commit fa1f57421e0b ("xen/virtio: Enable restricted memory access using
>> Xen grant mappings") introduced a new requirement for using virtio
>> devices: the backend now needs to support the VIRTIO_F_ACCESS_PLATFORM
>> feature.
>>
>> This is an undue requirement for non-PV guests, as those can be operated
>> with existing backends without any problem, as long as those backends
>> are running in dom0.
>>
>> Per default allow virtio devices without grant support for non-PV
>> guests.
>>
>> The setting can be overridden by using the new "xen_virtio_grant"
>> command line parameter.
>>
>> Add a new config item to always force use of grants for virtio.
>>
>> Fixes: fa1f57421e0b ("xen/virtio: Enable restricted memory access using Xen grant mappings")
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>>   .../admin-guide/kernel-parameters.txt         |  6 +++++
>>   drivers/xen/Kconfig                           |  9 ++++++++
>>   drivers/xen/grant-dma-ops.c                   | 22 +++++++++++++++++++
>>   include/xen/xen.h                             | 12 +++++-----
>>   4 files changed, 42 insertions(+), 7 deletions(-)
> 
> Thanks for the quick fix.
> 
> With CONFIG_DEBUG_SECTION_MISMATCH=y, this generates a warning.
> 
> WARNING: modpost: vmlinux.o(.text+0x7a8270): Section mismatch in reference from the function xen_set_restricted_virtio_memory_access() to the variable .init.data:xen_virtio_grants
> The function xen_set_restricted_virtio_memory_access() references
> the variable __initdata xen_virtio_grants.
> This is often because xen_set_restricted_virtio_memory_access lacks a __initdata
> annotation or the annotation of xen_virtio_grants is wrong.

Silly me. Thanks for the notice.

> 
> This can be fixed by:
> 
> diff --git a/drivers/xen/grant-dma-ops.c b/drivers/xen/grant-dma-ops.c
> index d1fae789dfad..1099097b4515 100644
> --- a/drivers/xen/grant-dma-ops.c
> +++ b/drivers/xen/grant-dma-ops.c
> @@ -42,7 +42,7 @@ static __init int parse_use_grants(char *arg)
>   }
>   early_param("xen_virtio_grant", parse_use_grants);
> 
> -void xen_set_restricted_virtio_memory_access(void)
> +void __init xen_set_restricted_virtio_memory_access(void)
>   {
>          if (IS_ENABLED(CONFIG_XEN_VIRTIO_FORCE_GRANT) || xen_virtio_grants ||
>              (!xen_virtio_grants_set && xen_pv_domain()))
> 
> With that:
> 
> Tested-by: Viresh Kumar <viresh.kumar@linaro.org>
> 

Thanks,


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2022-06-15  9:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  8:48 Juergen Gross
2022-06-15  9:25 ` Viresh Kumar
2022-06-15  9:32   ` Juergen Gross [this message]
2022-06-15 11:24 ` Christoph Hellwig
2022-06-15 11:26   ` Juergen Gross
2022-06-15 11:28     ` Christoph Hellwig
2022-06-15 11:39       ` Juergen Gross
2022-06-15 11:54         ` Christoph Hellwig
2022-06-15 12:53           ` Juergen Gross
2022-06-15 13:43             ` Christoph Hellwig
2022-06-15 13:46               ` Juergen Gross
2022-06-15 15:47 ` Oleksandr
2022-06-15 23:40 ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a063368a-022a-c294-5a19-da1b80c45461@suse.com \
    --to=jgross@suse.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=sstabellini@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®