From: "Zhao, Yu" <yu.zhao@intel.com>
To: Alexia Benington <alexbenington@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Option iommu=1 causes hypervisor to start debugger
Date: Wed, 04 Feb 2009 09:55:51 +0800 [thread overview]
Message-ID: <4988F5A7.9040703@intel.com> (raw)
In-Reply-To: <7969168f0902030625s1a652fd3x467d5fa595f8bc21@mail.gmail.com>
Which patch are you talking about? Since we can't get any clue from your
log, can you please send us the output of `lspci -vvv'?
Thanks,
Yu
Alexia Benington wrote:
> Thanks Keir. Perhaps I should try with Yu Zhao's patch and see if that
> fixes the problem.
>
> -Alex
>
> On Tue, Feb 3, 2009 at 3:06 AM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>> It's needed for passing through physical devices to HVM guests.
>>
>> -- Keir
>>
>> On 02/02/2009 23:42, "Alexia Benington" <alexbenington@gmail.com> wrote:
>>
>>> If I do not include the iommu option, I/O virtualisation is disabled.
>>> I never thought that iommu is a necessary prerequisite for I/O virt,
>>> or am I mistaken?
>>>
>>> -Alex
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>
>>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-02-04 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 21:16 Option iommu=1 causes hypervisor to start debugger Alexia Benington
2009-02-02 21:41 ` Keir Fraser
2009-02-02 21:48 ` Alexia Benington
2009-02-02 21:53 ` Neo Jia
2009-02-02 22:00 ` Alexia Benington
2009-02-02 23:42 ` Alexia Benington
2009-02-03 8:06 ` Keir Fraser
2009-02-03 14:25 ` Alexia Benington
2009-02-04 1:55 ` Zhao, Yu [this message]
2009-02-04 2:27 ` Alexia Benington
2009-02-04 2:52 ` Zhao, Yu
2009-02-04 20:30 ` Alexia Benington
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=4988F5A7.9040703@intel.com \
--to=yu.zhao@intel.com \
--cc=alexbenington@gmail.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.