From: Jan Kiszka
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
On 02/01/2012 06:43 AM, Jan Kiszka wrote:
On 2012-02-01 13:23, Paolo Bonzini wrote:
On 01/31/2012 10:49 PM, Jan Kiszka wrote:
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 whatev
On 2012-02-01 14:10, Jan Kiszka wrote:
> On 2012-02-01 13:55, Paolo Bonzini wrote:
>> On 02/01/2012 01:43 PM, Jan Kiszka wrote:
It looks good, besides the need to rebase to Anthony's "part 3" changes.
>>> Given that this part is not upstream and that the relevant conversion is
>>> scripted, I
On 2012-02-01 13:55, Paolo Bonzini wrote:
> On 02/01/2012 01:43 PM, Jan Kiszka wrote:
>>> It looks good, besides the need to rebase to Anthony's "part 3" changes.
>> Given that this part is not upstream and that the relevant conversion is
>> scripted, I would leave this to Anthony so far. Or what
On 02/01/2012 01:43 PM, Jan Kiszka wrote:
> It looks good, besides the need to rebase to Anthony's "part 3" changes.
Given that this part is not upstream and that the relevant conversion is
scripted, I would leave this to Anthony so far. Or what is the schedule?
By the time your series is revi
On 2012-02-01 13:23, Paolo Bonzini wrote:
> On 01/31/2012 10:49 PM, Jan Kiszka wrote:
>>> 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.
>
On 01/31/2012 10:49 PM, Jan Kiszka wrote:
> 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 th
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
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 o
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
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 p
11 matches
Mail list logo
