From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Zachary Amsden <zach@vmware.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"yhlu.kernel@gmail.com" <yhlu.kernel@gmail.com>,
Chris Wright <chrisw@sous-sol.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Rusty Russell <rusty@rustcorp.com.au>,
virtualization <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: let 32bit use apic_ops too - fix
Date: Tue, 15 Jul 2008 11:51:23 -0700 [thread overview]
Message-ID: <20080715185123.GA31445@linux-os.sc.intel.com> (raw)
In-Reply-To: <1216147130.6620.184.camel@bodhitayantram.eng.vmware.com>
On Tue, Jul 15, 2008 at 11:38:50AM -0700, Zachary Amsden wrote:
>
> Nacked-by: Zachary Amsden <zach@vmware.com>
>
> What are you doing here and why aren't you cc-ing the maintainers?
Sorry. I was about to bring you into the loop.
Yinghai posted 32bit native apic_ops(similar to my 64bit apic ops patch, which
is different from pv_apic_ops) which is in tip/x86/x2apic and proposed a fix
for VMI case aswell.
Based on my understanding, tip/x86/x2apic git commit
94a8c3c2437c8946f1b6c8e0b2c560a7db8ed3c6 is wrong and it should be fixed with
something like
http://marc.info/?l=linux-kernel&m=121614328831237&w=2
Can you please check and Ack/Nack this fix?
thanks,
suresh
next prev parent reply other threads:[~2008-07-15 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 18:38 Patch from LKML Zachary Amsden
2008-07-15 18:51 ` Suresh Siddha [this message]
2008-07-15 19:04 ` [PATCH] x86: let 32bit use apic_ops too - fix Zachary Amsden
2008-07-15 19:10 ` Yinghai Lu
2008-07-15 19:19 ` Zachary Amsden
2008-07-15 19:22 ` Yinghai Lu
2008-07-15 19:24 ` Zachary Amsden
2008-07-15 18:52 ` Patch from LKML Yinghai Lu
2008-07-15 18:57 ` Zachary Amsden
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=20080715185123.GA31445@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.org \
--cc=yhlu.kernel@gmail.com \
--cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).