qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [RFC][PATCH 14/16] kvm: x86: Add user space part for in-kernel i8259
Date: Sun, 04 Dec 2011 17:12:30 +0200	[thread overview]
Message-ID: <4EDB8DDE.5040402@redhat.com> (raw)
In-Reply-To: <4EDB7E62.7090909@web.de>

On 12/04/2011 04:06 PM, Jan Kiszka wrote:
> On 2011-12-04 15:04, Avi Kivity wrote:
> > On 12/04/2011 03:51 PM, Jan Kiszka wrote:
> >>>
> >>> But the name becomes part of the save/restore ABI, so you can't.
> >>
> >> Nope, the vmstate names are identical. That would ruin migration
> >> otherwise. It's just the output of info qtree & co. that changes.
> > 
> > Oh, okay.  I still think it's wrong, but now it's just a matter of
> > taste, and I can live with it.
>
> Wrong in what sense?

In the sense that kernel-apic is just an accelerated apic.  From the
guest point of view, there's no difference, and that should be reflected
in the device model.

If I'm reading an apic register, either from the guest or via a monitor
debug interface, I shouldn't care whether it's accelerated or not.  The
guest part already holds, of course.

> I think the way of merging kvm support into the user space models in
> qemu-kvm is not particularly beautiful. But that's my taste, and
> therefore I modeled the upstream proposal differently. :)

Oh, qemu-kvm was not meant to be an example of engineering elegance,
just minimal changes.

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

  reply	other threads:[~2011-12-04 15:12 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03 11:17 [Qemu-devel] [RFC][PATCH 00/16] uq/master: Introduce basic irqchip support Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 01/16] msi: Generalize msix_supported to msi_supported Jan Kiszka
2011-12-04 10:42   ` Michael S. Tsirkin
2011-12-04 10:42     ` Jan Kiszka
2011-12-04 13:12   ` Avi Kivity
2011-12-04 13:16     ` Jan Kiszka
2011-12-04 13:26       ` Avi Kivity
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 02/16] kvm: Move kvmclock into hw/kvm folder Jan Kiszka
2011-12-03 19:00   ` Andreas Färber
2011-12-03 22:33     ` Jan Kiszka
2011-12-04 10:43       ` Avi Kivity
2011-12-04 10:46         ` Jan Kiszka
2011-12-05 10:43       ` Andreas Färber
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 03/16] apic: Stop timer on reset Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 04/16] apic: Factor out core for KVM reuse Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 05/16] apic: Open-code timer save/restore Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 06/16] i8259: Factor out core for KVM reuse Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 07/16] ioapic: Convert to memory API Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 08/16] ioapic: Reject non-dword accesses to IOWIN register Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 09/16] ioapic: Factor out core for KVM reuse Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 10/16] memory: Introduce memory_region_init_reservation Jan Kiszka
2011-12-04 13:20   ` Avi Kivity
2011-12-04 13:24     ` Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 11/16] kvm: Introduce core services for in-kernel irqchip support Jan Kiszka
2011-12-04 13:23   ` Avi Kivity
2011-12-04 13:27     ` Jan Kiszka
2011-12-04 13:28       ` Avi Kivity
2011-12-04 13:30         ` Jan Kiszka
2011-12-04 13:32           ` Avi Kivity
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 12/16] kvm: x86: Establish IRQ0 override control Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 13/16] kvm: x86: Add user space part for in-kernel APIC Jan Kiszka
2011-12-04 13:24   ` Avi Kivity
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 14/16] kvm: x86: Add user space part for in-kernel i8259 Jan Kiszka
2011-12-04 13:31   ` Avi Kivity
2011-12-04 13:42     ` Jan Kiszka
2011-12-04 13:49       ` Avi Kivity
2011-12-04 13:51         ` Jan Kiszka
2011-12-04 14:04           ` Avi Kivity
2011-12-04 14:06             ` Jan Kiszka
2011-12-04 15:12               ` Avi Kivity [this message]
2011-12-04 15:19                 ` Jan Kiszka
2011-12-04 16:35                   ` Avi Kivity
2011-12-04 21:31                     ` Blue Swirl
2011-12-04 21:38                       ` Jan Kiszka
2011-12-05 10:01                         ` Avi Kivity
2011-12-05 11:37                           ` Jan Kiszka
2011-12-05 12:36                             ` Avi Kivity
2011-12-05 12:47                               ` Jan Kiszka
2011-12-05 13:14                                 ` Avi Kivity
2011-12-05 13:29                                   ` Jan Kiszka
2011-12-05 13:36                                     ` Avi Kivity
2011-12-05 13:55                                       ` Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 15/16] kvm: x86: Add user space part for in-kernel IOAPIC Jan Kiszka
2011-12-03 11:17 ` [Qemu-devel] [RFC][PATCH 16/16] kvm: Arm in-kernel irqchip support Jan Kiszka

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=4EDB8DDE.5040402@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --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 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 NNTP newsgroup(s).