From: Julien Grall <julien.grall@linaro.org>
To: Tamas K Lengyel <tamas.lengyel@zentific.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Tim Deegan <tim@xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] xen/arm: Implement domain_get_maximum_gpfn
Date: Mon, 08 Sep 2014 13:43:07 -0700 [thread overview]
Message-ID: <540E14DB.5000100@linaro.org> (raw)
In-Reply-To: <CAErYnshqvXfbS3sVa_pDScAenzaxi48qebDxw2JBPh27Bt0uqA@mail.gmail.com>
Hello Tamas,
On 03/09/14 02:00, Tamas K Lengyel wrote:
>
>
>
> On Wed, Sep 3, 2014 at 10:44 AM, Ian Campbell <Ian.Campbell@citrix.com
> <mailto:Ian.Campbell@citrix.com>> wrote:
>
> On Mon, 2014-09-01 at 17:32 -0400, Julien Grall wrote:
> > Hi Ian,
> >
> > On 16/07/14 12:02, Ian Campbell wrote:
> > > I'd much prefer to just have the fix to xc_dom_gnttab_hvm_seed
> for ARM
> > > and continue to punt on this interface until it is actually
> needed by
> > > something unavoidable on the guest side (and simultaneously
> hope that
> > > day never comes...).
> >
> > This patch is a requirement to make Xen Memory access working on ARM.
> > Could you reconsider the possibility to apply this patch on Xen?
>
> Needs more rationale as to why it is required for Xen Memory (do you
> mean xenaccess?). I assume I'll find that in the relevant thread once I
> get to it?
>
>
> It's used in a non-critical sanity check for performance reasons, as
> seen here:
> https://github.com/tklengyel/xen/blob/arm_memaccess3/xen/common/mem_access.c#L75.
> Without the sanity check we might attempt to set mem_access permissions
> on gpfn's that don't exist for the guest. It wouldn't break anything to
> do that but if we know beforehand that the gpfn is outside the scope of
> what the guest has we can skip the entire thing.
It might be better if you carry this patch on your series.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-09-08 20:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 14:57 [PATCH] xen/arm: Implement domain_get_maximum_gpfn Julien Grall
2014-07-01 16:57 ` Stefano Stabellini
2014-07-01 18:36 ` Julien Grall
2014-07-01 18:53 ` Andrew Cooper
2014-07-09 11:38 ` Julien Grall
2014-07-16 16:02 ` Ian Campbell
2014-07-16 18:17 ` Julien Grall
2014-09-01 21:32 ` Julien Grall
2014-09-03 8:44 ` Ian Campbell
2014-09-03 9:00 ` Tamas K Lengyel
2014-09-08 20:43 ` Julien Grall [this message]
2014-09-08 20:47 ` Tamas K Lengyel
2014-09-09 12:50 ` Tamas K Lengyel
2014-09-09 13:09 ` Andrew Cooper
2014-09-09 14:01 ` Tamas K Lengyel
2014-09-10 11:21 ` Tamas K Lengyel
2014-07-02 9:12 ` Ian Campbell
2014-07-02 9:19 ` Julien Grall
2014-07-02 9:22 ` Ian Campbell
2014-07-02 9:37 ` Julien Grall
2014-07-02 9:41 ` Ian Campbell
2014-07-02 9:50 ` Jan Beulich
2014-07-02 9:52 ` Ian Campbell
2014-07-02 10:19 ` Roger Pau Monné
2014-07-02 10:31 ` Jan Beulich
2014-07-02 10:51 ` Roger Pau Monné
2014-07-02 10:52 ` Ian Campbell
2014-07-02 10:58 ` Andrew Cooper
2014-07-02 11:21 ` Ian Campbell
2014-07-02 13:44 ` Konrad Rzeszutek Wilk
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=540E14DB.5000100@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tamas.lengyel@zentific.com \
--cc=tim@xen.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;
as well as URLs for NNTP newsgroup(s).