All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jambunathan K <jambunathan@netxen.com>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Sanjeev Jorapur <sanjeev@netxen.com>
Subject: Re: PCI Passthrough to HVM on xen-unstable
Date: Fri, 30 Nov 2007 19:33:37 +0530	[thread overview]
Message-ID: <47501839.2000504@netxen.com> (raw)
In-Reply-To: <08DF4D958216244799FC84F3514D70F0BB2571@pdsmsx415.ccr.corp.intel.com>

Han, Weidong wrote:
> Pls check your BIOS to see whether it's VT-d capable, and enable it
> first if you want to use it. Seems your configures are correct, pls
> check your BIOS.

I don't see an option for "Intel VT for Directed I/O" when "Intel Virtualization
Technology" is enabled. My understanding is that VT-d is a motherboard feature
and not a processor feature.

I have done some limited research looking around. I am confused whether I can
get VT-d to work with just a BIOS upgrade or I would be required to upgrade my
box altogther. If you have some info off the top of your head to clarify things
for me, I would appreciate it.

> Jambunathan K wrote:
>> (Resubmitting my original post with 'xm dmesg' output)
>>
>> I am working on S5000VSA Intel Server Board with the following cpu
>> spec. 
>>
>> XEN-PEER-RHEL5 $ cat /proc/cpuinfo
>> processor       : 0
>> vendor_id       : GenuineIntel
>> cpu family      : 6
>> model           : 15
>> model name      : Intel(R) Xeon(R) CPU           E5345  @ 2.33GHz
>> stepping        : 7
>> cpu MHz         : 2327.512
>> cache size      : 4096 KB
>> physical id     : 0
>> siblings        : 1
>> core id         : 0
>> cpu cores       : 1
>> fpu             : yes
>> fpu_exception   : yes
>> cpuid level     : 10
>> wp              : yes
>> flags           : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov
>> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm
>> constant_tsc up pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
>> bogomips        : 4661.90
>> clflush size    : 64
>> cache_alignment : 64
>> address sizes   : 36 bits physical, 48 bits virtual
>> power management:
>>
>> Is my box vt-d capable? If the answer is yes proceed ahead to the
>> details. If 
>> the answer is no, how can a novice user like me identify whether or
>> not his box 
>> is vt-d capable.
>>

  reply	other threads:[~2007-11-30 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 16:58 PCI Passthrough to HVM on xen-unstable Jambunathan K
2007-11-30  1:24 ` Han, Weidong
2007-11-30 14:03   ` Jambunathan K [this message]
2007-11-30 14:11     ` Han, Weidong
2007-11-30 15:10       ` Jambunathan K
2007-11-30 14:18     ` Li, Haicheng
  -- strict thread matches above, loose matches on Subject: below --
2007-11-29 16:52 Jambunathan K

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=47501839.2000504@netxen.com \
    --to=jambunathan@netxen.com \
    --cc=sanjeev@netxen.com \
    --cc=weidong.han@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.