mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	virtualization <virtualization@lists.osdl.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Ian Pratt <Ian.Pratt@xensource.com>,
	Christian Limpach <Christian.Limpach@cl.cam.ac.uk>,
	Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC PATCH 23/35] Increase x86 interrupt vector range
Date: Mon, 15 May 2006 14:57:20 -0700	[thread overview]
Message-ID: <20060515215720.GB25010@moss.sous-sol.org> (raw)
In-Reply-To: <200605131346_MC3-1-BFAF-FA0A@compuserve.com>

* Chuck Ebbert (76306.1226@compuserve.com) wrote:
> In-Reply-To: <20060509085157.070289000@sous-sol.org>
> 
> On Tue, 09 May 2006 00:00:23 -0700, Chris Wright wrote:
> 
> > Remove the limit of 256 interrupt vectors by changing the value
> > stored in orig_{e,r}ax to be the negated interrupt vector.
> > The orig_{e,r}ax needs to be < 0 to allow the signal code to
> > distinguish between return from interrupt and return from syscall.
> > With this change applied, NR_IRQS can be > 256.
> > 
> > Xen extends the IRQ numbering space to include room for dynamically
> > allocated virtual interrupts (in the range 256-511), which requires a
> > more permissive interface to do_IRQ.
> >
> > Signed-off-by: Ian Pratt <ian.pratt@xensource.com>
> > Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
> > Signed-off-by: Chris Wright <chrisw@sous-sol.org>
> > ---
> 
> AFAIC this could go in anytime.  It's simple, self-contained and makes
> sense even without Xen.

The plan is to split out things like this and push them ahead of the
rest of the batch.

> One minor nit: the IRQ value isn't negated, it's complemented.  The
> comments need to be fixed.

OK, bitwise negated.

thanks,
-chris

  parent reply	other threads:[~2006-05-15 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13 17:44 Chuck Ebbert
2006-05-14  7:52 ` Keir Fraser
2006-05-14 17:08   ` Ingo Oeser
2006-05-15 21:57 ` Chris Wright [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-09  8:49 [RFC PATCH 00/35] Xen i386 paravirtualization support Chris Wright
2006-05-09  7:00 ` [RFC PATCH 23/35] Increase x86 interrupt vector range Chris Wright

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=20060515215720.GB25010@moss.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=76306.1226@compuserve.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=Ian.Pratt@xensource.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.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®