kvm-ia64.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Otte <carsteno@de.ibm.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 0/7] Consolidate vcpu ioctl locking
Date: Fri, 21 May 2010 07:35:03 +0000	[thread overview]
Message-ID: <4BF637A7.3010203@de.ibm.com> (raw)
In-Reply-To: <1273749459-622-1-git-send-email-avi@redhat.com>

On 15.05.2010 10:26, Alexander Graf wrote:
> On S390, I'm also still sceptical if the implementation we have really works. A device injects an S390_INTERRUPT with its address and on the next vcpu_run, an according interrupt is issued. But what happens if two devices trigger an S390_INTERRUPT before the vcpu_run? We'd have lost an interrupt by then...
We're safe on that: the interrupt info field in both struct kvm (for 
floating interrupts) and struct vcpu (for cpu local interrupts) have 
their own locking and can queue up interrupts.

cheers,
Carsten

      parent reply	other threads:[~2010-05-21  7:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 11:17 [PATCH 0/7] Consolidate vcpu ioctl locking Avi Kivity
2010-05-13 11:57 ` Alexander Graf
2010-05-13 12:01 ` Avi Kivity
2010-05-13 12:03 ` Avi Kivity
2010-05-13 12:03 ` Avi Kivity
2010-05-13 12:18 ` Alexander Graf
2010-05-13 12:29 ` Avi Kivity
2010-05-13 19:49 ` Alexander Graf
2010-05-15 17:30 ` Avi Kivity
2010-05-16  1:00 ` Alexander Graf
2010-05-16  8:23 ` Avi Kivity
2010-05-16  9:01 ` Alexander Graf
2010-05-16  9:09 ` Avi Kivity
2010-05-16  9:35 ` Alexander Graf
2010-05-16  9:47 ` Avi Kivity
2010-05-16 10:19 ` Alexander Graf
2010-05-21  7:35 ` Carsten Otte [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=4BF637A7.3010203@de.ibm.com \
    --to=carsteno@de.ibm.com \
    --cc=kvm-ia64@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).