public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sheng Yang <sheng@linux.intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"avi@redhat.com" <avi@redhat.com>
Subject: Re: [PATCH v3] enable x2APIC without interrupt remapping under KVM
Date: Mon, 29 Jun 2009 18:10:16 +0300	[thread overview]
Message-ID: <20090629151016.GA8122@redhat.com> (raw)
In-Reply-To: <1246287519.27006.10660.camel@localhost.localdomain>

On Mon, Jun 29, 2009 at 07:58:39AM -0700, Suresh Siddha wrote:
> On Mon, 2009-06-29 at 06:29 -0700, Gleb Natapov wrote:
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index d1430ef..3e5b6ea 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -260,12 +260,15 @@ config SMP
> >  
> >  config X86_X2APIC
> >  	bool "Support x2apic"
> > -	depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP
> > +	depends on X86_LOCAL_APIC && X86_64
> 
> Thinking more, probably we shouldn't remove this dependency. This might
> encourage people (knowingly or unknowingly) to enable x2apic without
> interrupt-remapping. Can we remove this? KVM mode will still work even
> if we fail to enable interrupt-remapping. So this shouldn't be an issue,
> correct?
> 
Yes, KVM will still work. I don't have strong fillings one way or the
other, but why mandate an option that is no longer mandatory. What
others think?

> Sorry I should have commented about this before.
> 
> >  
> >  	ioapic_entries = alloc_ioapic_entries();
> >  	if (!ioapic_entries) {
> > -		pr_info("Allocate ioapic_entries failed: %d\n", ret);
> > -		goto end;
> > +		 pr_info("Allocate ioapic_entries failed\n");
> > +		 return;
> 
> 
> We should go to ir_failed ..
Why? There is not more ir_failed.

> 
> >  	}
> >  
> >  	ret = save_IO_APIC_setup(ioapic_entries);
> >  	if (ret) {
> >  		pr_info("Saving IO-APIC state failed: %d\n", ret);
> > -		goto end;
> > +		free_ioapic_entries(ioapic_entries);
> > +		return;
> 
> same here.
> 
Why? What ir_failed should do? Call free_ioapic_entries(ioapic_entries)
and exit?

--
			Gleb.

  reply	other threads:[~2009-06-29 15:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 13:29 [PATCH v3] enable x2APIC without interrupt remapping under KVM Gleb Natapov
2009-06-29 14:58 ` Suresh Siddha
2009-06-29 15:10   ` Gleb Natapov [this message]
2009-06-29 15:15     ` Suresh Siddha
2009-06-29 15:45       ` Gleb Natapov
2009-06-30  9:24 ` Eric W. Biederman
2009-06-30  9:26   ` Gleb Natapov
2009-06-30 16:44     ` Eric W. Biederman
2009-06-30 17:12       ` Avi Kivity
2009-06-30 19:08         ` Eric W. Biederman
2009-06-30 19:16           ` Avi Kivity
2009-06-30 19:36             ` Eric W. Biederman
2009-07-01  8:30               ` Avi Kivity
2009-07-01 13:31                 ` Eric W. Biederman
2009-07-01 22:53               ` Suresh Siddha
2009-07-02  0:17                 ` Eric W. Biederman
2009-07-07 16:14                   ` Suresh Siddha
2009-07-10 20:29                     ` Eric W. Biederman
2009-06-30 19:03       ` Gleb Natapov
2009-06-30 19:43         ` Eric W. Biederman

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=20090629151016.GA8122@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox