From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>,
Juergen Gross <jgross@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 3/3] xen/virtio: enable grant based virtio on x86
Date: Fri, 7 Oct 2022 12:01:37 -0400 [thread overview]
Message-ID: <79358304-de2e-3025-f147-cba2f76f22d2@oracle.com> (raw)
In-Reply-To: <67c9ec7d-a67d-ca28-4354-68e38aa27e13@epam.com>
On 10/7/22 10:00 AM, Oleksandr Tyshchenko wrote:
> On 07.10.22 09:41, Juergen Gross wrote:
>
> Hello Juergen
>
>> Use an x86-specific virtio_check_mem_acc_cb() for Xen in order to setup
>> the correct DMA ops.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>> V2:
>> - add missing PV check in xen_virtio_mem_acc() (Oleksandr Tyshchenko)
>> - add xen_virtio_restricted_mem_acc() stub (Oleksandr Tyshchenko)
>
> Reviewed-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> #
> common code
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
prev parent reply other threads:[~2022-10-07 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 6:41 [PATCH v2 0/3] xen/virtio: support " Juergen Gross
2022-10-07 6:41 ` [PATCH v2 1/3] xen/virtio: restructure xen grant dma setup Juergen Gross
2022-10-07 6:41 ` [PATCH v2 2/3] xen/virtio: use dom0 as default backend for CONFIG_XEN_VIRTIO_FORCE_GRANT Juergen Gross
2022-10-07 6:41 ` [PATCH v2 3/3] xen/virtio: enable grant based virtio on x86 Juergen Gross
2022-10-07 14:00 ` Oleksandr Tyshchenko
2022-10-07 16:01 ` Boris Ostrovsky [this message]
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=79358304-de2e-3025-f147-cba2f76f22d2@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Oleksandr_Tyshchenko@epam.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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®