mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Andi Kleen <andi@firstfloor.org>, "hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [RFC 1/4]x86: cleanup vector usage
Date: Sat, 06 Nov 2010 13:45:34 +0800	[thread overview]
Message-ID: <1289022334.2029.3.camel@shli-laptop> (raw)
In-Reply-To: <20101105205516.GB5678@lenovo>

On Sat, 2010-11-06 at 04:55 +0800, Cyrill Gorcunov wrote:
> On Wed, Nov 03, 2010 at 02:44:18PM +0800, Shaohua Li wrote:
> > Cleanup the vector usage and make them continuous if possible.
> > 
> > Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> > ---
> ...
> > -#define X86_PLATFORM_IPI_VECTOR		0xed
> > +#define X86_PLATFORM_IPI_VECTOR		0xf7
> >  
> >  /*
> >   * IRQ work vector:
> >   */
> > -#define IRQ_WORK_VECTOR			0xec
> > +#define IRQ_WORK_VECTOR			0xf6
> >  
> > -#define UV_BAU_MESSAGE			0xea
> > +#define UV_BAU_MESSAGE			0xf5
> >  
> >  /*
> >   * Self IPI vector for machine checks
> >   */
> > -#define MCE_SELF_VECTOR			0xeb
> > +#define MCE_SELF_VECTOR			0xf4
> >  
> >  /* Xen vector callback to receive events in a HVM domain */
> > -#define XEN_HVM_EVTCHN_CALLBACK		0xe9
> > +#define XEN_HVM_EVTCHN_CALLBACK		0xf3
> > +
> 
>  Hi Li, this is not just a cleanup -- irq priority were changed as
> well, but I suppose it's harmless ;)
I didn't change the local apic timer vector because the comments say the
priority is important. For others, I do suppose it's harmless.


  reply	other threads:[~2010-11-06  5:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03  6:44 Shaohua Li
2010-11-05 20:55 ` Cyrill Gorcunov
2010-11-06  5:45   ` Shaohua Li [this message]
2010-11-06  9:10     ` Cyrill Gorcunov

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=1289022334.2029.3.camel@shli-laptop \
    --to=shaohua.li@intel.com \
    --cc=andi@firstfloor.org \
    --cc=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®