From: David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
To: xen-devel@lists.sourceforge.net
Subject: Re: Porting of Guest OS
Date: Fri, 31 Dec 2004 07:40:33 +0000 [thread overview]
Message-ID: <41D50271.7050806@blueyonder.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0412301857040.14925@linux.site>
Ronald G. Minnich wrote:
> On Thu, 30 Dec 2004, Amitabh Tamhane wrote:
>
>>During boot-up:
>>1) Applying Intel IA32 Microcode update: insmod:
>>/lib/modules/2.6.5-7.97-smp/kernel/arch/i386/kernel/microcode.o: insmod
>>char-major-10-184 failed
>
> is it safe to assume that code in Ring 1 can't upgrade microcode :-)?
> I'd say that the microcode module would surprise me if it worked.
It should be possible to make it work by using the hypervisor interface
equivalents of rdmsr/wrmsr. See section 9.11 of the IA32 architecture
manual Volume 3.
Does DOM0 always run on all physical CPU cores?
--
David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2004-12-31 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 0:12 Porting of Guest OS Amitabh Tamhane
2004-12-30 2:58 ` Fajar A. Nugraha
2004-12-30 8:14 ` Amitabh Tamhane
2004-12-30 8:35 ` Fajar A. Nugraha
2004-12-30 14:50 ` M.A. Williamson
2004-12-31 1:14 ` Amitabh Tamhane
2004-12-31 1:58 ` Ronald G. Minnich
2004-12-31 7:40 ` David Hopwood [this message]
2004-12-31 7:49 ` Fajar A. Nugraha
2004-12-31 8:02 ` David Hopwood
2004-12-31 15:40 ` Ronald G. Minnich
2005-01-01 2:26 ` David Hopwood
2004-12-31 9:53 ` Keir Fraser
2004-12-31 15:44 ` Ronald G. Minnich
2004-12-31 15:42 ` M.A. Williamson
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 0:13 Amitabh Tamhane
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=41D50271.7050806@blueyonder.co.uk \
--to=david.nospam.hopwood@blueyonder.co.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.