From: "Jan Beulich" <jbeulich@novell.com>
To: Mark Langsdorf <mark.langsdorf@amd.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: dom0 and apicid not equal to cpuid
Date: Wed, 13 Feb 2008 09:23:55 +0000 [thread overview]
Message-ID: <47B2C53B.76E4.0078.0@novell.com> (raw)
In-Reply-To: <6453C3CB8E2B3646B0D020C11261327309377B@sausexmb4.amd.com>
>>> "Langsdorf, Mark" <mark.langsdorf@amd.com> 12.02.08 20:09 >>>
>> On 12/2/08 15:33, "Langsdorf, Mark" <mark.langsdorf@amd.com> wrote:
>> >> In the non-pinned case perhaps we should initialise all those
>> >> arrays to -1 for sanity's sake.
>> >
>> > If this had been done initially, I'd think it was a good idea,
>> > but I'm worried about introducing that kind of change now.
>>
>> It's fine not to change this case if you don't want to. It
>> would probably logically belong in a separate patch anyway.
>
>Is there an easy way to get Xen to pass the "cpufreq=dom0-kernel"
>hypervisor argument onto to the Linux command line? I can
>add a separate parament to Linux easily enough, but I'd like it
>if the end-user didn't need to add it twice.
You could do this along with the other similar stuff in
xen/arch/x86/setup.c:__start_xen() (following the comment "Grab
the DOM0 command line.")
Jan
next prev parent reply other threads:[~2008-02-13 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 21:05 dom0 and apicid not equal to cpuid Langsdorf, Mark
2008-02-08 21:19 ` Keir Fraser
2008-02-08 21:22 ` Keir Fraser
2008-02-14 22:16 ` Mark Langsdorf
2008-02-14 22:22 ` Keir Fraser
2008-02-11 22:38 ` Langsdorf, Mark
2008-02-11 23:08 ` Keir Fraser
2008-02-12 10:29 ` Keir Fraser
2008-02-12 15:33 ` Langsdorf, Mark
2008-02-12 16:43 ` Keir Fraser
2008-02-12 19:09 ` Langsdorf, Mark
2008-02-13 9:23 ` Jan Beulich [this message]
2008-02-13 10:07 ` Keir Fraser
2008-02-13 10:04 ` Keir Fraser
2008-02-13 22:52 ` Mark Langsdorf
2008-02-14 8:26 ` Keir Fraser
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=47B2C53B.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=mark.langsdorf@amd.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.