linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: julien.grall@linaro.org (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Extend zImage format to support notes
Date: Wed, 09 Apr 2014 17:31:00 +0100	[thread overview]
Message-ID: <534575C4.2020906@linaro.org> (raw)
In-Reply-To: <20140407182553.GD14062@e106331-lin.cambridge.arm.com>

Hi Mark,

On 04/07/2014 07:25 PM, Mark Rutland wrote:
> 
> I'm probably being thick here, but is there anything preventing those
> foreign pages from being idmapped into DOM0 (at least for the duration
> of the DMA access) such that there is a 1-1 PA<->IPA mapping?
> 
> That would mean that from the point of view of Linux, there's nothing to
> care about, as every address it knows it can deal with is a valid IPA.
> Existing kernels would function with the IOMMU(s) on.
> 
> I assume I'm missing something fairly obvious :)

I didn't though about this solution. It works on midway only when the
physical address size is 32 bits.

I didn't yet figure out why. I guess this is because I have a bug in my
SMMU driver in Xen.

>> We though about runtime approach (see the whole discussion here
>> https://patches.linaro.org/26034/), but it's not as extensible as notes.
>> In fact, we might need more notes in the future when new feature will be
>> added and requires a DOM0/guest side support.
> 
> I can certainly see the usefulness of notes.

[..]

> If it makes sense for this case then I can see why we would want it on
> arm64.

With the solution of idmapping, the RFC seems irrelevant for now. But we
may need to add notes in the future.

I'm wondering if it would be worth to agree on a solution now. Thus, we
will be able to add a note quickly when it will be necessary.

Any thoughts?

Sincerely yours,

-- 
Julien Grall

      reply	other threads:[~2014-04-09 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 13:59 [RFC] Extend zImage format to support notes Julien Grall
2014-04-07 16:04 ` Mark Rutland
2014-04-07 17:28   ` Julien Grall
2014-04-07 18:25     ` Mark Rutland
2014-04-09 16:31       ` 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=534575C4.2020906@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).