From: Bob Liu <bob.liu@oracle.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: xen-devel@lists.xenproject.org, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, linux-kernel@vger.kernel.org,
"David Vrabel" <david.vrabel@citrix.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH 0/2] block/xen-blkfront: Support non-indirect with 64KB page granularity
Date: Sat, 12 Sep 2015 17:46:08 +0800 [thread overview]
Message-ID: <55F3F460.7000702@oracle.com> (raw)
In-Reply-To: <1441999920-3639-1-git-send-email-julien.grall@citrix.com>
Hi Julien,
On 09/12/2015 03:31 AM, Julien Grall wrote:
> Hi all,
>
> This is a follow-up on the previous discussion [1] related to guest using 64KB
> page granularity not booting with backend using non-indirect grant.
>
> This has been successly tested on ARM64 with both 64KB and 4KB page granularity
> guests and QEMU as the backend. Indeed QEMU is not supported indirect.
>
What's the linux kernel page granularity of the backend(dom0) in your test?
Did you test if using xen-blkback as the backend? Especially when linux kernel page
granularity of dom0 is 4kB while domU is 64KB.
Thanks,
-Bob
> For a summary of the previous discussion see patch #2.
>
> This series is based on top of my 64KB page granularity support [2].
>
> Comments are welcomed.
>
> Sincerely yours,
>
> [1] http://lists.xen.org/archives/html/xen-devel/2015-08/msg01659.html
> [2] https://lwn.net/Articles/656797/
>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: "Roger Pau Monné" <roger.pau@citrix.com>
> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Cc: David Vrabel <david.vrabel@citrix.com>
>
> Julien Grall (2):
> block/xen-blkfront: Introduce blkif_ring_get_request
> block/xen-blkfront: Handle non-indirect grant with 64KB pages
>
> drivers/block/xen-blkfront.c | 229 ++++++++++++++++++++++++++++++++++++++-----
> 1 file changed, 202 insertions(+), 27 deletions(-)
>
next prev parent reply other threads:[~2015-09-12 9:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 19:31 [PATCH 0/2] block/xen-blkfront: Support non-indirect with 64KB page granularity Julien Grall
2015-09-11 19:31 ` [PATCH 1/2] block/xen-blkfront: Introduce blkif_ring_get_request Julien Grall
2015-10-05 15:22 ` Roger Pau Monné
2015-09-11 19:32 ` [PATCH 2/2] block/xen-blkfront: Handle non-indirect grant with 64KB pages Julien Grall
2015-10-05 16:01 ` Roger Pau Monné
2015-10-05 17:05 ` [Xen-devel] " Julien Grall
2015-10-06 9:39 ` Roger Pau Monné
2015-10-06 9:58 ` Julien Grall
2015-10-06 10:06 ` Roger Pau Monné
2015-10-12 18:00 ` Julien Grall
2015-10-19 11:16 ` Roger Pau Monné
2015-10-19 11:36 ` Julien Grall
2015-09-12 9:46 ` Bob Liu [this message]
2015-09-13 12:06 ` [Xen-devel] [PATCH 0/2] block/xen-blkfront: Support non-indirect with 64KB page granularity Julien Grall
2015-09-13 12:44 ` Bob Liu
2015-09-13 17:47 ` Julien Grall
2015-09-14 0:37 ` Bob Liu
2015-10-02 9:32 ` Julien Grall
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=55F3F460.7000702@oracle.com \
--to=bob.liu@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).