All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Kevin O'Connor" <kevin@koconnor.net>
Cc: seabios@seabios.org, kvm@vger.kernel.org
Subject: Re: [PATCH RFC] acpi: add ssdt for cpi hotplug
Date: Thu, 3 Nov 2011 14:31:18 +0200	[thread overview]
Message-ID: <20111103123117.GI18296@redhat.com> (raw)
In-Reply-To: <20111103003028.GA16459@morn.localdomain>

On Wed, Nov 02, 2011 at 08:30:28PM -0400, Kevin O'Connor wrote:
> On Wed, Nov 02, 2011 at 10:54:42AM +0200, Michael S. Tsirkin wrote:
> > On Tue, Nov 01, 2011 at 06:59:01PM -0400, Kevin O'Connor wrote:
> > > Can we leave these parts in the DSDT and only move the bulk generated
> > > stuff to the SSDT?
> > > 
> > They can, but I thought one of the reasons we do the split
> > is to make it possible for users to supply their own DSDT?
> > If so creating calls from SSDT into DSDT would make this very fragile.
> 
> I think it's reasonable to require that a user supplied DSDT still
> fill certain requirements.  Keep in mind that the reason for the "user
> supplied" DSDT was for new platform (q35) development - not
> necessarily so each individual user could set their own.
> 
> It's not great to have the DSDT and SSDT tied to each other.  However,
> once RMV is removed, it's only two methods (PCNT supplied by the SSDT
> and PCEJ supplied by the DSDT).
> 
> I do see the upside to moving it all to the SSDT - but that has the
> disadvantage of taking away the ability of a user supplied DSDT to
> tweak how the hotplug functions work.

Is this something q35 needs?

>  Also, we'd then want to redo CPU hotplug to be the same way.

OK, I'll do that if we decide this is a good direcction.

> -Kevin

  parent reply	other threads:[~2011-11-03 12:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 19:11 [PATCH RFC] acpi: add ssdt for cpi hotplug Michael S. Tsirkin
2011-11-01 22:59 ` Kevin O'Connor
2011-11-02  8:54   ` Michael S. Tsirkin
2011-11-03  0:30     ` Kevin O'Connor
2011-11-03  1:04       ` [SeaBIOS] " Wen Congyang
2011-11-03  1:36         ` Kevin O'Connor
2011-11-03  2:14           ` [SeaBIOS] " Wen Congyang
2011-11-03 12:33           ` Michael S. Tsirkin
2011-11-03 12:31       ` Michael S. Tsirkin [this message]
2011-11-04  6:00         ` [SeaBIOS] " Isaku Yamahata
2011-11-02  6:08 ` Wen Congyang
2011-11-02  7:20   ` Wen Congyang

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=20111103123117.GI18296@redhat.com \
    --to=mst@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=kvm@vger.kernel.org \
    --cc=seabios@seabios.org \
    /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.