From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH 2] HVM vcpu add/remove: setup dsdt and madt infrastructure for vcpu add/remove
Date: Wed, 09 Dec 2009 12:04:56 +0000 [thread overview]
Message-ID: <C74542E8.3F41%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C7453880.3F27%keir.fraser@eu.citrix.com>
On 09/12/2009 11:20, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
> What's PROC_BASE, and what's APIC_MADT_PTR? No comments attached to them:
> they look like random magic numbers.
>
> DSDT code generation can be done in mk_dsdt.c, rather then addign
> preprocessor stuff to the static part of the DSDT in dsdt.asl. So move stuff
> there instead.
>
> What's the MADT checksum stuff in the DSDT all about? Does the MADT really
> have to stay consistent and checksummed after boot - I would have assumed
> that it provides a boot-time snapshot of the system only, and would not be
> looked at by the OSPM after boot. I haven't looked at the ASL code in detail
> but I'll surely bet that the approach is fragile.
Ah, this has to do with the _MAT methods doesn't it. Well, I wonder whether
the strategy of sharing the _MAT return values and the MADT entries is
actually sensible. There seems to be no really good reason to do it -- they
should be consistent at boot-time of course, but after boot the MADT isn't
expected to remain live and up-to-date I believe? Then each Processor object
can define its own MAT buffer which it manages entirely by and for itself.
-- Keir
next prev parent reply other threads:[~2009-12-09 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <706158FABBBA044BAD4FE898A02E4BC201CF7CA2D3@pdsmsx503.ccr.corp.intel.com>
2009-12-09 11:20 ` [PATCH 2] HVM vcpu add/remove: setup dsdt and madt infrastructure for vcpu add/remove Keir Fraser
2009-12-09 12:04 ` Keir Fraser [this message]
2009-12-09 12:21 ` Keir Fraser
2009-12-09 13:52 ` Christoph Egger
2009-12-09 15:18 ` Keir Fraser
2009-12-10 12:08 ` Liu, Jinsong
2009-12-10 20:14 ` 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=C74542E8.3F41%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=jinsong.liu@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.