xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Arianna Avanzini <avanzini.arianna@gmail.com>, xen-devel@lists.xen.org
Cc: paolo.valente@unimore.it, Ian Campbell <Ian.Campbell@citrix.com>,
	stefano.stabellini@eu.citrix.com, dario.faggioli@citrix.com,
	Tim Deegan <tim@xen.org>,
	julien.grall@citrix.com, etrudeau@broadcom.com,
	viktor.kleinik@globallogic.com
Subject: Re: [RFC PATCH 2/3] arch, arm32: add the XEN_DOMCTL_memory_mapping hypercall
Date: Thu, 06 Mar 2014 11:41:15 +0800	[thread overview]
Message-ID: <5317EE5B.6070602@linaro.org> (raw)
In-Reply-To: <53172DBF.7010900@gmail.com>



On 05/03/14 21:59, Arianna Avanzini wrote:
> Hello,

Hello Arianna,

>> The comment "1:1 iomem mapping (gfn == mfn)" seems wrong here. The
>> implementation you wrote allow gfn != mfn.
>>
>
> Right, thank you.
> Sorry if I bother you with one more question about this hunk; aside from the
> error pointed out by Eric with the usage of pfn instead of paddr_t, is it OK to
> map the address range all at once with map_mmio_regions() as proposed? I noticed
> that the x86-related code seems to map the range one mfn at a time with
> set_mmio_p2m_entry(), and I wonder if this different approach has any benefit I
> didn't think about.

map_mmio_regions will take p2m lock and do MMU management (e.g TLB 
flush...). For the latter the code  has been written to only do TLB 
flush, if needed, once per call. More the range is large, better it is.

So, it's better to call the function only once for the whole range.

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-03-06  3:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02  0:49 [RFC PATCH 0/3] Implement the XEN_DOMCTL_memory_mapping hypecall for arm32 Arianna Avanzini
2014-03-02  0:49 ` [RFC PATCH 1/3] arch, arm32: add definition of paddr_bits Arianna Avanzini
2014-03-02  8:13   ` Julien Grall
2014-03-07  0:36     ` Arianna Avanzini
2014-03-02  0:49 ` [RFC PATCH 2/3] arch, arm32: add the XEN_DOMCTL_memory_mapping hypercall Arianna Avanzini
2014-03-02  9:56   ` Julien Grall
2014-03-03 11:56     ` Dario Faggioli
2014-03-03 15:20       ` Julien Grall
2014-03-03 15:33         ` Dario Faggioli
2014-03-04  2:42           ` Julien Grall
2014-03-07  0:47             ` Arianna Avanzini
2014-03-03 16:25         ` Eric Trudeau
2014-03-03 16:35           ` Dario Faggioli
2014-03-03 19:04             ` Eric Trudeau
2014-03-05 13:59     ` Arianna Avanzini
2014-03-06  3:41       ` Julien Grall [this message]
2014-03-07  0:57         ` Arianna Avanzini
2014-03-03 18:06   ` Eric Trudeau
2014-03-04  3:08     ` Julien Grall
2014-03-07  0:56       ` Arianna Avanzini
2014-03-07  3:41         ` Julien Grall
2014-03-07 19:49           ` Arianna Avanzini
2014-03-02  0:49 ` [RFC PATCH 3/3] tools, libxl: handle the iomem parameter with the memory_mapping hcall Arianna Avanzini
2014-03-02 10:33   ` Julien Grall
2014-03-02 11:27     ` Ian Campbell
2014-03-03 10:32       ` Dario Faggioli
2014-03-03 15:13         ` Julien Grall
2014-03-07  0:45           ` Arianna Avanzini
2014-03-07  4:03             ` Julien Grall
2014-03-07 19:54               ` Arianna Avanzini
2014-03-03 11:19     ` Dario Faggioli
2014-03-07  4:05       ` Julien Grall
2014-03-02  8:13 ` [RFC PATCH 0/3] Implement the XEN_DOMCTL_memory_mapping hypecall for arm32 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=5317EE5B.6070602@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=avanzini.arianna@gmail.com \
    --cc=dario.faggioli@citrix.com \
    --cc=etrudeau@broadcom.com \
    --cc=julien.grall@citrix.com \
    --cc=paolo.valente@unimore.it \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=viktor.kleinik@globallogic.com \
    --cc=xen-devel@lists.xen.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).