All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Han, Weidong" <weidong.han@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
	'George Dunlap' <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: [RFC][PATCH] 0/9 Populate-on-demand memory
Date: Fri, 26 Dec 2008 08:42:49 +0800	[thread overview]
Message-ID: <715D42877B251141A38726ABF5CABF2C018E8961FD@pdsmsx503.ccr.corp.intel.com> (raw)
In-Reply-To: <0A882F4D99BBF6449D58E61AAFD7EDD603BB4A08@pdsmsx502.ccr.corp.intel.com>

Tian, Kevin wrote:
>> From: Han, Weidong
>> Sent: Thursday, December 25, 2008 1:43 PM
>>>> 
>>>> At any rate, until we have that worked out, we should probably add
>>>> some "seatbelt" code to make sure that people don't use PoD for a
>>>> VT-d enabled domain.  I know absolutely nothing about the VT-d
>>>> code; could you either write a patch to do this check, or give me
>>>> an idea of the simplest thing to check?
>>> 
>>> Weidong works on VT-d and could give comments on exact point to
>>> check. 
>>> 
>> 
>> You can simply check "iommu_enabled" to know whether IOMMU
>> including VT-d and AMD IOMMU is used or not.
>> 
> 
> Weidong, does iommu_enabled indicate IOMMU h/w availability?
> Then you'll have this nice feature disabled on most new platform
> with IOMMU shipped. :-) Here a domain-based check is required,
> i.e. PoD is only appliable when target domain is not passthroughed
> with any device.
> 
> Thanks,
> Kevin

iommu_enabled will be set when IOMMU h/w is available and user sets "iommu=1" in grub to use it. Because device hotplug with VT-d is already supported, I think domain-based check is not enough, it's better to disable PoD when iommu_enabled is set. 

Regards,
Weidong

      reply	other threads:[~2008-12-26  0:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23 12:55 [RFC][PATCH] 0/9 Populate-on-demand memory George Dunlap
2008-12-23 19:06 ` Dan Magenheimer
2008-12-24 13:55   ` George Dunlap
2008-12-24 14:32     ` Dan Magenheimer
2008-12-24 15:13       ` George Dunlap
2008-12-24 15:54         ` Dan Magenheimer
2008-12-24  1:46 ` Tian, Kevin
2008-12-24 14:42   ` George Dunlap
2008-12-24 15:35     ` Dan Magenheimer
2008-12-24 15:46       ` George Dunlap
2008-12-30  9:26         ` Tim Deegan
2008-12-31  1:40           ` Tian, Kevin
2009-01-02 10:03             ` Tim Deegan
2009-01-05  6:08               ` Tian, Kevin
2008-12-25  2:47       ` Tian, Kevin
2008-12-25  2:36     ` Tian, Kevin
2008-12-25  5:43       ` Han, Weidong
2008-12-25 11:45         ` Tian, Kevin
2008-12-26  0:42           ` Han, Weidong [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=715D42877B251141A38726ABF5CABF2C018E8961FD@pdsmsx503.ccr.corp.intel.com \
    --to=weidong.han@intel.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=kevin.tian@intel.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.