From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH 1/3] iommu: set correct IOMMU entries when iommu_hap_pt_share == 0
Date: Tue, 8 Apr 2014 11:19:31 +0200 [thread overview]
Message-ID: <5343BF23.1000408@citrix.com> (raw)
In-Reply-To: <5343CFD4020000780000672B@nat28.tlf.novell.com>
On 08/04/14 10:30, Jan Beulich wrote:
>>>> On 07.04.14 at 18:02, <roger.pau@citrix.com> wrote:
>> If the memory map is not shared between HAP and IOMMU we fails to set
>> correct IOMMU mappings for memory types different than p2m_ram_rw.
>>
>> This patchs adds IOMMU support for the following memory types:
>> p2m_grant_map_rw, p2m_map_foreign, p2m_ram_ro and p2m_grant_map_ro.
>
> I'm curious about the justification for p2m_map_foreign; the others
> I agree with.
Thanks for the review, I didn't see a reason to not allow DMA transfers
to/from foreign pages, although there's no user of foreign pages that
use DMA.
>
> I also wonder whether p2m_ram_logdirty shouldn't be treated
> equally to p2m_ram_rw: It's clearly better to have some video
> corruption than to kill the guest due to excessive IOMMU faults,
> should its kernel choose to DMA into the frame buffer. But at the
> very minimum this needs to be included alongside p2m_ram_ro.
Ack. I wasn't sure about p2m_ram_logdirty, so I just decided to not
include it. I will add it to my next revision as a RW zone if that's fine.
Roger.
next prev parent reply other threads:[~2014-04-08 9:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 16:02 [PATCH 0/3] Fix grant map/unmap with auto-translated guests Roger Pau Monne
2014-04-07 16:02 ` [PATCH 1/3] iommu: set correct IOMMU entries when iommu_hap_pt_share == 0 Roger Pau Monne
2014-04-07 16:49 ` Konrad Rzeszutek Wilk
2014-04-08 8:30 ` Jan Beulich
2014-04-08 9:19 ` Roger Pau Monné [this message]
2014-04-08 9:55 ` Jan Beulich
2014-04-08 14:12 ` Tim Deegan
2014-04-08 15:15 ` Roger Pau Monné
2014-04-08 15:29 ` Jan Beulich
2014-04-13 20:27 ` Tim Deegan
2014-04-16 14:36 ` Roger Pau Monné
2014-04-16 14:41 ` Jan Beulich
2014-04-07 16:02 ` [PATCH 2/3] amd-iommu: disable iommu_hap_pt_share with AMD IOMMUs Roger Pau Monne
2014-04-07 16:51 ` Konrad Rzeszutek Wilk
2014-04-07 16:54 ` George Dunlap
2014-04-08 7:29 ` Roger Pau Monné
2014-04-08 8:52 ` Jan Beulich
2014-04-08 14:16 ` Tim Deegan
2014-04-08 14:36 ` Jan Beulich
2014-04-08 15:39 ` Roger Pau Monné
2014-04-07 16:02 ` [PATCH 3/3] xen: expose that grant table mappings update the IOMMU Roger Pau Monne
2014-04-08 8:34 ` Ian Campbell
2014-04-08 8:56 ` Jan Beulich
2014-04-08 8:58 ` Ian Campbell
2014-04-08 9:53 ` Jan Beulich
2014-04-08 9:57 ` Ian Campbell
2014-04-08 10:05 ` Jan Beulich
2014-04-08 10:26 ` Ian Campbell
2014-04-08 10:31 ` Jan Beulich
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=5343BF23.1000408@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.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).