All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2] HVM vcpu add/remove: setup dsdt and madt infrastructure for vcpu add/remove
Date: Thu, 10 Dec 2009 20:14:01 +0000	[thread overview]
Message-ID: <C7470709.41CF%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC201CF7CA731@pdsmsx503.ccr.corp.intel.com>

On 10/12/2009 12:08, "Liu, Jinsong" <jinsong.liu@intel.com> wrote:

>> What's PROC_BASE, and what's APIC_MADT_PTR? No comments attached to
>> them: they look like random magic numbers.
> 
> KVM has vcpu add/remove code, these 2 items learn from KVM qemu/vbios/dsdt
> code.
> Since they belong to qemu & vbios part, I think we'd better keep same with
> KVM.
> I will add comments for them at updated patch.

Oh, I categorically do not care about keeping these magic numbers the same
as KVM/qemu. If there are some ioports or iomem emulated at fixed address by
qemu then that's one thing, but keeping their vbios random numbers when we
*do not use* the same vbios makes no sense.

I'd rather keep our MADT layout, add a few lines of code to hvmloader to
describe some MADT position/layout parameters to the DSDT via the bios_info
structure, and go from there. Smaller, clearer patch, as far as I can see.

 -- Keir

      reply	other threads:[~2009-12-10 20:14 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
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 [this message]

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=C7470709.41CF%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.