xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH] xen: arm: Enable 1:1 workaround by default
Date: Wed, 27 Nov 2013 13:43:37 +0000	[thread overview]
Message-ID: <5295F709.5020107@linaro.org> (raw)
In-Reply-To: <1385558785.23112.189.camel@kazak.uk.xensource.com>



On 11/27/2013 01:26 PM, Ian Campbell wrote:
> On Wed, 2013-11-27 at 13:23 +0000, Julien Grall wrote:
>>
>> On 11/27/2013 12:19 PM, Ian Campbell wrote:
>>> I was just about to send out patches adding the 1:1 workaround to vexpress (the
>>> foundation model is a vexpress platfrom with DMA) and sunxi.
>>>
>>> That would have meant that all platforms now implement the quirk. Instead lets
>>> just make it the default and remove the quirk.
>>>
>>> In the future this will likely be set based on the presence absence of an
>>> IOMMU, perhaps with additional overrides by the platform.
>>>
>>> A command line option no-dom0_11_mapping is provided.
>>>
>>
>> I plan to use the variable in other place, for instance in
>> common/memory.c to solve issue between ballooning and 1:1 workaround.
>>
>> It would be great if we have a function (platform_has_iommu) that we can
>> use everywhere. What do you think?
>
> I think in reality once iommu's arrive it will be a bit more subtle than
> their presence or absence, e.g. something (perhaps the platform code)
> will need to decide if all the write devices are behind an iommu such
> that the 11 can be disabled.
>
> I can unstatic opt_dom0_11_mapping and stick it in a header though. Or
> provide an accessor method.

An accessor method sounds better.

-- 
Julien Grall

      reply	other threads:[~2013-11-27 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 12:19 [PATCH] xen: arm: Enable 1:1 workaround by default Ian Campbell
2013-11-27 12:20 ` Andrew Cooper
2013-11-27 12:23   ` Ian Campbell
2013-11-27 12:24     ` Andrew Cooper
2013-11-29 12:50     ` Stefano Stabellini
2013-11-27 13:23 ` Julien Grall
2013-11-27 13:26   ` Ian Campbell
2013-11-27 13:43     ` Julien Grall [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=5295F709.5020107@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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).