All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] VMX: inject high priority interrupts first
Date: Thu, 13 Dec 2007 18:29:35 +0200	[thread overview]
Message-ID: <47615DEF.2010204@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A0281F361-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 774 bytes --]

Dong, Eddie wrote:
> This is not necessary, vector doesn;t mean priority.
>
> Remember I ever had a talk with Avi that user level irqchip could only support
> one vector pending in kernel like you mentioned too. On the other hand,
> if we have multiple pending vectors, we will lose priority. The point here
> is that vector doesn;t stand for priority for example slave PIC has higher priority
> than IRQ3-7 of master PIC. Using ffs or fls doesn;t matter here.
>
>   

Yes.

> But I think we'd better clean the code to just use pending_vector instead
> of bitmap to reduce those kind of unnecessary bit scan/set/clear etc.
>   

That's my plan; use a pending vector and put it in subarch independent code.


-- 
error compiling committee.c: too many arguments to function



[-- Attachment #2: Type: text/plain, Size: 308 bytes --]

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

      parent reply	other threads:[~2007-12-13 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 13:17 [PATCH] VMX: inject high priority interrupts first Dor Laor
     [not found] ` <47613102.1020200-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-13 15:54   ` Dong, Eddie
     [not found]     ` <10EA09EFD8728347A513008B6B0DA77A0281F361-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-13 16:29       ` Avi Kivity [this message]

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=47615DEF.2010204@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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.