qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
	Avi Kivity <avi@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/4] i8254: Factor out base class for KVM reuse
Date: Tue, 31 Jan 2012 15:59:36 -0600	[thread overview]
Message-ID: <4F286448.8010002@us.ibm.com> (raw)
In-Reply-To: <4F2861F4.1000604@web.de>

On 01/31/2012 03:49 PM, Jan Kiszka wrote:
> On 2012-01-31 22:40, Anthony Liguori wrote:
>> On 01/31/2012 12:46 PM, Jan Kiszka wrote:
>>> Applying the concept used for the *PICs once again: establish a base
>>> class for the i8254 that can be used both by the current user space
>>> emulation and the upcoming KVM in-kernel version. We share most of the
>>> public interface of the i8254, specifically to the pcspk, vmstate, reset
>>> and certain init parts.
>>>
>>> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>
>>
>> Now that we have QOM bits, there's no need to factor out a common base
>> class.
>>
>> Just make the methods that you want to override virtual with the default
>> implementation and then make a KVMPIT that inherits from the PIT and
>> then overrides whatever virtual functions it needs to.
>
> That doesn't sound like the proper design for this purpose.

It's hard to say really.  There's a lot more in the common class that I expected 
(like initialization of the ISA regions.  I would expect the base class to look 
a lot more like an interface such that the KVM PIT implementation was 
trivialized more than it is.

But I can argue it both ways so if you feel strongly here, I won't object.

Regards,

Anthony Liguori

  Rather, we
> have an abstract base class that both implementations are derived from.
> If I'm not using QOM properly to achieve this, please tell me.
>
> Thanks,
> Jan

  reply	other threads:[~2012-01-31 22:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 18:46 [Qemu-devel] [PATCH 0/4] uq/master: Introduce KVM PIT support Jan Kiszka
2012-01-31 18:46 ` [Qemu-devel] [PATCH 1/4] i8254: Factor out base class for KVM reuse Jan Kiszka
2012-01-31 21:40   ` Anthony Liguori
2012-01-31 21:49     ` Jan Kiszka
2012-01-31 21:59       ` Anthony Liguori [this message]
2012-02-01 12:23       ` Paolo Bonzini
2012-02-01 12:43         ` Jan Kiszka
2012-02-01 12:55           ` Paolo Bonzini
2012-02-01 13:10             ` Jan Kiszka
2012-02-01 13:11               ` Jan Kiszka
2012-02-01 13:19           ` Anthony Liguori
2012-01-31 18:46 ` [Qemu-devel] [PATCH 2/4] i8254: Open-code timer restore Jan Kiszka
2012-01-31 18:46 ` [Qemu-devel] [PATCH 3/4] kvm: Add kvm_has_pit_state2 helper Jan Kiszka
2012-01-31 18:46 ` [Qemu-devel] [PATCH 4/4] kvm: x86: Add user space part for in-kernel i8254 Jan Kiszka
  -- strict thread matches above, loose matches on Subject: below --
2012-02-05 10:46 [Qemu-devel] [PATCH 0/4] uq/master: Introduce KVM PIT support Jan Kiszka
2012-02-05 10:46 ` [Qemu-devel] [PATCH 1/4] i8254: Factor out base class for KVM reuse 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=4F286448.8010002@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --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).