From: Wen Congyang <wency@cn.fujitsu.com>
To: "Kevin O'Connor" <kevin@koconnor.net>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
seabios@seabios.org, kvm@vger.kernel.org
Subject: Re: [SeaBIOS] [PATCH RFC] acpi: add ssdt for cpi hotplug
Date: Thu, 03 Nov 2011 09:04:57 +0800 [thread overview]
Message-ID: <4EB1E8B9.7050408@cn.fujitsu.com> (raw)
In-Reply-To: <20111103003028.GA16459@morn.localdomain>
At 11/03/2011 08:30 AM, Kevin O'Connor Write:
> 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.
I do not think it's reasonable to require that a user supplied DSDT still
fill certain requiements.
I think we should not use default SSDT if we use user supplied DSDT.
If we use user supplied DSDT, we should use user supplied SSDT too.
Thanks
Wen Congyang
>
> 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. Also, we'd then want to redo
> CPU hotplug to be the same way.
>
> -Kevin
>
> _______________________________________________
> SeaBIOS mailing list
> SeaBIOS@seabios.org
> http://www.seabios.org/mailman/listinfo/seabios
>
next prev parent reply other threads:[~2011-11-03 1:03 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 ` Wen Congyang [this message]
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
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=4EB1E8B9.7050408@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).