public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: "kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	"Zhang,
	 Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Hollis Blanchard
	<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: RFC/patch 2/2: remove irq.h include in kvm_main.c
Date: Thu, 22 Nov 2007 17:47:36 +0100	[thread overview]
Message-ID: <4745B2A8.9040702@de.ibm.com> (raw)
In-Reply-To: <4745B039.20108-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Avi Kivity wrote:
> I generally understand "irq" to mean the interrupt request line, and 
> "interrupt" to mean a vectored interrupt (post interrupt controller).  
> In those terms the naming in correct.  However I'm not at all certain 
> this naming convention is generally accepted.
I think on s390 we'll have

kvm_s390_vcpu_has_extint()
kvm_s390_vcpu_has_ioint()
and maybe
kvm_s390_vcpu_has_machine_check()

and kvm_arch_vcpu_has_interrupt() will check if any of above is 
pending. It would be great if the function names would clearly 
identify that one is the general portable "cpu needs to run an 
interrupt handler of whatever sort" and the other one is "we have a 
vectored interrupt to deliver" on x86 as well. If you'd like to keep 
the wording as is, I'll send a patch that just adds the 
kvm_arch_cpu_has_interrupt wrapper.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-11-22 16:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-22 16:24 RFC/patch 1/2: remove desc.h include in kvm_main.c Carsten Otte
     [not found] ` <1195748641.22845.3.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-11-22 16:30   ` RFC/patch 2/2: remove irq.h " Carsten Otte
     [not found]     ` <1195749032.22845.10.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-11-22 16:37       ` Avi Kivity
     [not found]         ` <4745B039.20108-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-22 16:42           ` Cornelia Huck
     [not found]             ` <20071122174230.52d6f4bd-XQvu0L+U/CiXI4yAdoq52KN5r0PSdgG1zG2AekJRRhI@public.gmane.org>
2007-11-22 16:45               ` Avi Kivity
     [not found]                 ` <4745B217.9080202-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-22 16:49                   ` Avi Kivity
2007-11-22 17:20               ` Cornelia Huck
2007-11-22 16:47           ` Carsten Otte [this message]
     [not found]             ` <4745B2A8.9040702-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-11-22 16:52               ` Avi Kivity
2007-11-22 16:34   ` RFC/patch 1/2: remove desc.h " Avi Kivity
2007-11-22 23:11   ` Zhang, Xiantao

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=4745B2A8.9040702@de.ibm.com \
    --to=cotte-ta70fqpds9bqt0dzr+alfa@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
    --cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox