From: "Ren, Qiaowei" <qiaowei.ren@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
"Maliszewski, Richard L" <richard.l.maliszewski@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tboot-devel@lists.sourceforge.net"
<tboot-devel@lists.sourceforge.net>,
Xiaoyan Zhang <xiaoyan.zhang@intel.com>,
"Wei, Gang" <gang.wei@intel.com>
Subject: RE: [PATCH v2] x86: add a new SMP bring up way for tboot case
Date: Thu, 11 Apr 2013 07:16:38 +0000 [thread overview]
Message-ID: <9E0BE1322F2F2246BD820DA9FC397ADE507CDA@SHSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <514926C0.3020502@zytor.com>
> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa@zytor.com]
> Sent: Wednesday, March 20, 2013 11:02 AM
> To: Ren, Qiaowei
> Cc: Thomas Gleixner; Ingo Molnar; x86@kernel.org; Maliszewski, Richard L;
> linux-kernel@vger.kernel.org; tboot-devel@lists.sourceforge.net; Xiaoyan
> Zhang; Wei, Gang
> Subject: Re: [PATCH v2] x86: add a new SMP bring up way for tboot case
>
> On 03/19/2013 07:14 PM, Ren, Qiaowei wrote:
> > Any comments on this patch?
> >
> > Thanks,
> > Qiaowei
>
> The biggest question is probably if we can use an existing hook of some sort.
>
> Overriding the apic method is probably not the right way to go, though.
> tglx, do you have any opinions here?
>
If we can't use an existing hook, could you please give me any suggestion about other opinions here?
> Furthermore, this really is not nice:
>
> > +int tboot_wake_up(int apicid, unsigned long sipi_vec) {
> > + if (!tboot_enabled())
> > + return 0;
> > +
> > + if ((tboot->version < 6) ||
> > + !(tboot->flags & TB_FLAG_AP_WAKE_SUPPORT))
> > + return 0;
> > +
> > + tboot->ap_wake_addr = sipi_vec;
> > + tboot->ap_wake_trigger = apicid;
> > +
> > + return 1;
> > +}
>
> Not only don't you set boot_error for the code above it, but there is absolutely
> no indication how that does its job (are those active operations? If so they
> should use writel()), nor does it include any kind of synchronization.
>
Ok. I should add some comments to explain how that does its job.
But I guess boot_error don't have to be set inside this function.
Thanks,
Qiaowei
prev parent reply other threads:[~2013-04-11 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 10:11 Qiaowei Ren
2012-11-14 11:14 ` Wei, Gang
2013-03-20 2:14 ` Ren, Qiaowei
2013-03-20 3:02 ` H. Peter Anvin
2013-04-11 7:16 ` Ren, Qiaowei [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=9E0BE1322F2F2246BD820DA9FC397ADE507CDA@SHSMSX102.ccr.corp.intel.com \
--to=qiaowei.ren@intel.com \
--cc=gang.wei@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richard.l.maliszewski@intel.com \
--cc=tboot-devel@lists.sourceforge.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xiaoyan.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®