mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Christoph Hellwig <hch@infradead.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 15:46:59 +0200	[thread overview]
Message-ID: <0a1501fc-e03f-8a1d-76a1-c115606c6278@suse.com> (raw)
In-Reply-To: <Yqnh7vjO8iT4/fiK@infradead.org>


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

On 15.06.22 15:43, Christoph Hellwig wrote:
> On Wed, Jun 15, 2022 at 02:53:54PM +0200, Juergen Gross wrote:
>> On 15.06.22 13:54, Christoph Hellwig wrote:
>>> On Wed, Jun 15, 2022 at 01:39:01PM +0200, Juergen Gross wrote:
>>>> No, it doesn't. I'm working on a qemu patch series enabling the qemu
>>>> based backends to support grants with virtio. The code is working fine
>>>> on x86, too (apart from the fact that the backends aren't ready yet).
>>>
>>> The code right now in mainline only ever sets the ops for DMA.  So
>>> I can't see how you could make it work.
>>
>> Ah, you are right. I was using a guest with an older version of the series.
>> Sorry for the noise.
> 
> No problem.  But whatever you end up using to enable the grant DMA
> ops n x86 should also require the platform access feature.  We already
> have that information so we can make use of it.

Yes, of course.


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 13:47 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
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 [this message]
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=0a1501fc-e03f-8a1d-76a1-c115606c6278@suse.com \
    --to=jgross@suse.com \
    --cc=corbet@lwn.net \
    --cc=hch@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=sstabellini@kernel.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®