All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Merging kvm-apic into qemu-kvm
Date: Thu, 26 Jan 2012 16:25:10 +0100	[thread overview]
Message-ID: <4F217056.1030609@siemens.com> (raw)
In-Reply-To: <4F216E19.3040905@redhat.com>

On 2012-01-26 16:15, Avi Kivity wrote:
> The changes to kvm-apic are so drastic, that merging them into qemu-kvm
> in the normal way won't work.  I can consider just dropping the existing
> implementation and switching to the new one, but the comment at the end
> 
>     Make the basic in-kernel irqchip support selectable via
>     -machine ...,kernel_irqchip=on. Leave it off by default until it can
>     fully replace user space models.
> 
> suggests that things are still missing.
> 
> Jan, what's still missing?

- in-kernel PIT (patches done, waiting for some upstream bits to be
  merged first)
- TPR acceleration via VAPIC (WIP)
- MSI support

The latter is the big chunk. It requires quite some
refactoring/enhancement of the MSI layer. I posted the first version
last year. We need to agree on the design, then probably switch qemu-kvm
over while pushing generic bits upstream. And then we can extend the
upstream in-kernel *PIC using that new interfaces. Once upstream works
with MSI, we can switch qemu-kvm over, leaving basically only
device-assignment as the last missing bit.

>  Any idea on how to proceed?

I had a qemu-kvm branch here that disables the upstream in-kernel *PIC
in favor of its current version. I still need to refresh that work (was
based on an earlier revision), but it was not that horrible. Let me check...

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Merging kvm-apic into qemu-kvm
Date: Thu, 26 Jan 2012 16:25:10 +0100	[thread overview]
Message-ID: <4F217056.1030609@siemens.com> (raw)
In-Reply-To: <4F216E19.3040905@redhat.com>

On 2012-01-26 16:15, Avi Kivity wrote:
> The changes to kvm-apic are so drastic, that merging them into qemu-kvm
> in the normal way won't work.  I can consider just dropping the existing
> implementation and switching to the new one, but the comment at the end
> 
>     Make the basic in-kernel irqchip support selectable via
>     -machine ...,kernel_irqchip=on. Leave it off by default until it can
>     fully replace user space models.
> 
> suggests that things are still missing.
> 
> Jan, what's still missing?

- in-kernel PIT (patches done, waiting for some upstream bits to be
  merged first)
- TPR acceleration via VAPIC (WIP)
- MSI support

The latter is the big chunk. It requires quite some
refactoring/enhancement of the MSI layer. I posted the first version
last year. We need to agree on the design, then probably switch qemu-kvm
over while pushing generic bits upstream. And then we can extend the
upstream in-kernel *PIC using that new interfaces. Once upstream works
with MSI, we can switch qemu-kvm over, leaving basically only
device-assignment as the last missing bit.

>  Any idea on how to proceed?

I had a qemu-kvm branch here that disables the upstream in-kernel *PIC
in favor of its current version. I still need to refresh that work (was
based on an earlier revision), but it was not that horrible. Let me check...

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-01-26 15:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 15:15 Merging kvm-apic into qemu-kvm Avi Kivity
2012-01-26 15:15 ` [Qemu-devel] " Avi Kivity
2012-01-26 15:25 ` Jan Kiszka [this message]
2012-01-26 15:25   ` Jan Kiszka
2012-01-26 15:32   ` Jan Kiszka
2012-01-26 15:32     ` [Qemu-devel] " Jan Kiszka
2012-01-26 15:39     ` Avi Kivity
2012-01-26 15:39       ` [Qemu-devel] " Avi Kivity
2012-01-26 15:45       ` Jan Kiszka
2012-01-26 15:45         ` [Qemu-devel] " Jan Kiszka
2012-01-26 15:49         ` Avi Kivity
2012-01-26 15:49           ` [Qemu-devel] " Avi Kivity
2012-01-27 21:34           ` Jan Kiszka
2012-01-27 21:34             ` [Qemu-devel] " Jan Kiszka
2012-01-29 10:33             ` Avi Kivity
2012-01-29 10:33               ` [Qemu-devel] " Avi Kivity
2012-01-29 11:12               ` Avi Kivity
2012-01-29 11:12                 ` [Qemu-devel] " Avi Kivity
2012-01-29 11:15                 ` Jan Kiszka
2012-01-29 11:15                   ` [Qemu-devel] " Jan Kiszka
2012-01-29 11:18                   ` Avi Kivity
2012-01-29 11:18                     ` [Qemu-devel] " Avi Kivity
2012-01-29 11:20                     ` Jan Kiszka
2012-01-29 11:20                       ` [Qemu-devel] " Jan Kiszka
2012-01-29 11:54                     ` Jan Kiszka
2012-01-29 11:54                       ` [Qemu-devel] " Jan Kiszka
2012-01-29 12:01                       ` Avi Kivity
2012-01-29 12:01                         ` [Qemu-devel] " Avi Kivity
2012-01-29 12:02                         ` Jan Kiszka
2012-01-29 12:02                           ` [Qemu-devel] " Jan Kiszka
2012-01-29 12:04                           ` Avi Kivity
2012-01-29 12:04                             ` [Qemu-devel] " Avi Kivity
2012-01-29 12:06                             ` Avi Kivity
2012-01-29 12:06                               ` [Qemu-devel] " Avi Kivity
2012-01-29 12:35                               ` Avi Kivity
2012-01-29 12:35                                 ` [Qemu-devel] " Avi Kivity
2012-01-29 15:56                                 ` Avi Kivity
2012-01-29 15:56                                   ` [Qemu-devel] " Avi Kivity

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=4F217056.1030609@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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.