From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: "dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] new hvm platform vhpet enable parameter
Date: Thu, 14 Feb 2008 21:50:40 +0000 [thread overview]
Message-ID: <C3DA6830.13DFE%Keir.Fraser@cl.cam.ac.uk> (raw)
In-Reply-To: <20080214124819656.00000001516@djm-pc>
On 14/2/08 19:48, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
>> It enables it by default if the tools do not explicitly
>> instruct either way.... for old saved guest images...
>
> OK, I see. I'm glad you caught that.
>
> But does that mean if a guest config file does not explicitly
> have a "hpet = 0" line, the default will be on? If so,
> that's different from how I intended. Perhaps the
> code in XendDomainInfo _constructDomain should be modified
> to set it to zero if "hpet is None"? Else, I'll bet
> guests created by virt-install will end up with hpet on.
Yes, that's possible. Possibly XendConfig.py should set a default. Or
virt-install itself should do so.
> Also it occurs to me it might be a good idea to add a
> gdprintk in hvm.c so that whether the hpet is on or not
> is visibly logged.
There are many config options for an HVM guest, none of which are logged by
Xen. It would be inconsistent to log just this one.
-- Keir
next prev parent reply other threads:[~2008-02-14 21:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 17:46 [PATCH] new hvm platform vhpet enable parameter Dan Magenheimer
2008-02-07 17:52 ` Samuel Thibault
2008-02-07 17:53 ` Keir Fraser
2008-02-07 18:29 ` Dan Magenheimer
2008-02-07 18:37 ` Keir Fraser
2008-02-07 20:53 ` Dan Magenheimer
2008-02-14 16:52 ` Dan Magenheimer
2008-02-14 17:52 ` Keir Fraser
2008-02-14 18:18 ` Dan Magenheimer
2008-02-14 19:25 ` Keir Fraser
2008-02-14 19:48 ` Dan Magenheimer
2008-02-14 21:50 ` Keir Fraser [this message]
2008-02-08 12:50 ` Stephen C. Tweedie
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=C3DA6830.13DFE%Keir.Fraser@cl.cam.ac.uk \
--to=keir.fraser@cl.cam.ac.uk \
--cc=dan.magenheimer@oracle.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.