public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: mingo@elte.hu, gorcunov@gmail.com, kvm@vger.kernel.org
Subject: Re: [PATCH 2/2] kvm tools: inject MSI directly without going through a GSI
Date: Sat, 04 Aug 2012 11:30:19 +0200	[thread overview]
Message-ID: <501CEBAB.1040504@gmail.com> (raw)
In-Reply-To: <CAOJsxLFOUjoezkVrvijjWmpBUCyYBh1GrZ2TJQSnRUgredbJ8g@mail.gmail.com>

On 08/04/2012 11:14 AM, Pekka Enberg wrote:
> Hi Sasha,
> 
> On Thu, Aug 2, 2012 at 5:29 PM, Sasha Levin <levinsasha928@gmail.com> wrote:
>> Use the new KVM_SIGNAL_MSI ioctl to inject interrupts directly.
>>
>> We still create GSIs and keep them for two reasons:
>>
>>  - They're required by virtio-* devices.
>>  - There's not much overhead since we just create them when starting the
>> guest, they don't use anything when the guest is running.
>>
>> Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
> 
> This patch makes 'make check' hang for me. Full boot log below:

Is your host kernel running 3.5? The new MSI injection ioctl is a new 3.5 feature.


  reply	other threads:[~2012-08-04  9:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 14:29 [PATCH 1/2] kvm tools: prevent guest softlockup errors when pausing Sasha Levin
2012-08-02 14:29 ` [PATCH 2/2] kvm tools: inject MSI directly without going through a GSI Sasha Levin
2012-08-04  9:14   ` Pekka Enberg
2012-08-04  9:30     ` Sasha Levin [this message]
2012-08-04 11:02       ` Pekka Enberg
2012-08-05  7:02         ` Sasha Levin
2012-08-05  9:08           ` Pekka Enberg
2012-08-05  9:14             ` Sasha Levin
2012-08-05  9:31               ` Pekka Enberg

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=501CEBAB.1040504@gmail.com \
    --to=levinsasha928@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@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