All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	Gleb Natapov <gleb@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sheng Yang <sheng@linux.intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v5] enable x2APIC without interrupt remapping under KVM
Date: Sat, 04 Jul 2009 18:20:10 +0300	[thread overview]
Message-ID: <4A4F732A.4050103@redhat.com> (raw)
In-Reply-To: <20090703082905.GF21833@elte.hu>

On 07/03/2009 11:29 AM, Ingo Molnar wrote:
> Now, since this affects core x86 APIC code non-trivially so should
> submitted to and go via the x86 tree. (Can prepare a special branch
> with just this change if KVM tree wants/needs to pull it before
> v2.6.32.)
>    

The kvm tree won't depend on this change.  I'm happy with it going into 
2.6.32 via tip.git.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  parent reply	other threads:[~2009-07-04 15:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 13:30 [PATCH v5] enable x2APIC without interrupt remapping under KVM Gleb Natapov
2009-07-01 21:00 ` Suresh Siddha
2009-07-03  8:29   ` Ingo Molnar
2009-07-04  9:35     ` Eric W. Biederman
2009-07-04  9:55       ` Gleb Natapov
2009-07-04 14:33         ` Eric W. Biederman
2009-07-04 15:50           ` Gleb Natapov
2009-07-05  0:22             ` Eric W. Biederman
2009-07-05  5:27               ` Avi Kivity
2009-07-04 15:20     ` Avi Kivity [this message]
2009-07-05 14:32     ` [PATCH] " Gleb Natapov
2009-07-10 13:56       ` Ingo Molnar
2009-07-12 12:06         ` Gleb Natapov
2009-07-18 14:07           ` Ingo Molnar

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=4A4F732A.4050103@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sheng@linux.intel.com \
    --cc=suresh.b.siddha@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 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.