From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Auger Eric <eric.auger@redhat.com>,
eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, stefanha@redhat.com, fam@euphon.net,
alex.williamson@redhat.com
Cc: kwolf@redhat.com, mreitz@redhat.com
Subject: Re: [RFC 0/5] NVMe passthrough: Support 64kB page host
Date: Thu, 15 Oct 2020 20:01:56 +0200 [thread overview]
Message-ID: <920515f6-aae8-41fa-007a-701bdd6cdf1c@redhat.com> (raw)
In-Reply-To: <d3ba4c98-67b8-0d38-378a-805fb02b3d40@redhat.com>
On 10/15/20 6:15 PM, Auger Eric wrote:
> Hi Philippe,
>
> On 10/15/20 3:49 PM, Philippe Mathieu-Daudé wrote:
>> On 10/15/20 1:52 PM, Eric Auger wrote:
>>> This series allows NVMe passthrough on aarch64 with 64kB page host.
>>> Addresses and sizes of buffers which are VFIO DMA mapped are
>>> aligned with the host page size.
>>>
>>> nvme_register_buf() path is taken care of in this series
>>> but it does not seem to prevent the use case from working.
>>>
>>> Best Regards
>>>
>>> Eric
>>>
>>> This series can be found at:
>>> https://github.com/eauger/qemu/tree/nvme_64k_rfc
>>>
>>> This was tested on ARM only.
>>>
>>> Eric Auger (5):
>>> block/nvme: use some NVME_CAP_* macros
>>> block/nvme: Change size and alignment of IDENTIFY response buffer
>>> block/nvme: Change size and alignment of queue
>>> block/nvme: Change size and alignment of prp_list_pages
>>> block/nvme: Align iov's va and size on host page size
>>
>> Since it is easier for me to rebase on top of your series,
>> I'm including it in my work (fixing the checkpatch errors)
>> and will repost block/nvme/ patches altogether.
>
> There should be one warning (line exceeding 80 chars) but no error. I
> can easily rebase/respin if you prefer.
Yes, warnings, no error. No need to respin.
>
> Thanks
>
> Eric
>>
>> Regards,
>>
>> Phil.
>>
>>
>
prev parent reply other threads:[~2020-10-15 18:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 11:52 [RFC 0/5] NVMe passthrough: Support 64kB page host Eric Auger
2020-10-15 11:52 ` [RFC 1/5] block/nvme: use some NVME_CAP_* macros Eric Auger
2020-10-15 13:29 ` Philippe Mathieu-Daudé
2020-10-15 13:32 ` Philippe Mathieu-Daudé
2020-10-15 13:36 ` Philippe Mathieu-Daudé
2020-10-15 16:11 ` Auger Eric
2020-10-15 11:52 ` [RFC 2/5] block/nvme: Change size and alignment of IDENTIFY response buffer Eric Auger
2020-10-20 10:59 ` Philippe Mathieu-Daudé
2020-10-20 11:31 ` Philippe Mathieu-Daudé
2020-10-15 11:52 ` [RFC 3/5] block/nvme: Change size and alignment of queue Eric Auger
2020-10-15 11:52 ` [RFC 4/5] block/nvme: Change size and alignment of prp_list_pages Eric Auger
2020-10-15 11:52 ` [RFC 5/5] block/nvme: Align iov's va and size on host page size Eric Auger
2020-10-20 11:33 ` Philippe Mathieu-Daudé
2020-10-15 13:49 ` [RFC 0/5] NVMe passthrough: Support 64kB page host Philippe Mathieu-Daudé
2020-10-15 16:15 ` Auger Eric
2020-10-15 18:01 ` Philippe Mathieu-Daudé [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=920515f6-aae8-41fa-007a-701bdd6cdf1c@redhat.com \
--to=philmd@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).