From: Avi Kivity <avi@redhat.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: kvm@vger.kernel.org, "Kay, Allen M" <allen.m.kay@intel.com>,
"Yang, Sheng" <sheng.yang@intel.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Amit Shah <amit.shah@redhat.com>,
Ben-Ami Yassour1 <BENAMI@il.ibm.com>
Subject: Re: [PATCH] [RESEND] VT-d: Fix iommu map page for mmio pages
Date: Thu, 02 Oct 2008 15:29:38 +0300 [thread overview]
Message-ID: <48E4BEB2.2000403@redhat.com> (raw)
In-Reply-To: <20081002120906.GE7289@il.ibm.com>
Muli Ben-Yehuda wrote:
> On Thu, Oct 02, 2008 at 02:56:55PM +0300, Avi Kivity wrote:
>
>> Han, Weidong wrote:
>>
>>> From 61028d958dc7c57ee02de32ea89b025dccb9650d Mon Sep 17 00:00:00 2001
>>> From: Weidong Han <weidong.han@intel.com>
>>> Date: Thu, 25 Sep 2008 23:32:02 +0800
>>> Subject: [PATCH] Map mmio pages into VT-d page table
>>>
>>> Assigned device could DMA to mmio pages, so also need to map mmio pages
>>> into VT-d page table.
>>>
>>>
>>>
>> Well, Muli says at least on one machine this allows on guest to kill
>> the host. What are we doing with this?
>>
>> If it's a hardware bug which is planned to be fixed (or is already
>> fixed), great, but I need to know.
>>
>
> Unfortunately I don't have access to the machine any more. We did
> spend some time perusing the PCIe spec on this point, and although it
> is pretty vague, the bottom line appears to be that peer-to-peer
> traffic (device-to-device traffic) is allowed. I'm fine with applying
> the patch.
>
Okay, I applied the patch.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-10-02 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 15:41 [PATCH] [RESEND] VT-d: Fix iommu map page for mmio pages Han, Weidong
2008-10-02 11:56 ` Avi Kivity
2008-10-02 12:09 ` Muli Ben-Yehuda
2008-10-02 12:29 ` Avi Kivity [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=48E4BEB2.2000403@redhat.com \
--to=avi@redhat.com \
--cc=BENAMI@il.ibm.com \
--cc=allen.m.kay@intel.com \
--cc=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=sheng.yang@intel.com \
/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).