From: "Andreas Färber" <afaerber@suse.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: anthony.perard@citrix.com, pbonzini@redhat.com,
aliguori@us.ibm.com, xen-devel@lists.xensource.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] xen: remove xen_vcpu_init
Date: Thu, 30 May 2013 18:46:54 +0200 [thread overview]
Message-ID: <51A7827E.3050706@suse.de> (raw)
In-Reply-To: <1369678631-821-1-git-send-email-stefano.stabellini@eu.citrix.com>
Am 27.05.2013 20:17, schrieb Stefano Stabellini:
> No need for xen_vcpu_init anymore:
>
> - the RTC emulator doesn't have any periodic timers continuously running
> even in absence of guest interactions anymore;
>
> - qemu_dummy_start_vcpu takes care of disabling TCG for us, so we don't
> need to do it manually here.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> ---
> hw/i386/pc_piix.c | 1 -
> xen-all.c | 23 -----------------------
> 2 files changed, 0 insertions(+), 24 deletions(-)
Reviewed-by: Andreas Färber <afaerber@suse.de>
and I've queued a copy on qom-cpu since this facilitates my upcoming
first_cpu refactoring.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
WARNING: multiple messages have this Message-ID (diff)
From: "Andreas Färber" <afaerber@suse.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: anthony.perard@citrix.com, pbonzini@redhat.com,
aliguori@us.ibm.com, xen-devel@lists.xensource.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] xen: remove xen_vcpu_init
Date: Thu, 30 May 2013 18:46:54 +0200 [thread overview]
Message-ID: <51A7827E.3050706@suse.de> (raw)
In-Reply-To: <1369678631-821-1-git-send-email-stefano.stabellini@eu.citrix.com>
Am 27.05.2013 20:17, schrieb Stefano Stabellini:
> No need for xen_vcpu_init anymore:
>
> - the RTC emulator doesn't have any periodic timers continuously running
> even in absence of guest interactions anymore;
>
> - qemu_dummy_start_vcpu takes care of disabling TCG for us, so we don't
> need to do it manually here.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> ---
> hw/i386/pc_piix.c | 1 -
> xen-all.c | 23 -----------------------
> 2 files changed, 0 insertions(+), 24 deletions(-)
Reviewed-by: Andreas Färber <afaerber@suse.de>
and I've queued a copy on qom-cpu since this facilitates my upcoming
first_cpu refactoring.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-05-30 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 18:16 [Qemu-devel] [PATCH 0/2] Xen cleanups Stefano Stabellini
2013-05-27 18:16 ` Stefano Stabellini
2013-05-27 18:17 ` [Qemu-devel] [PATCH 1/2] xen: remove xen_vcpu_init Stefano Stabellini
2013-05-27 18:17 ` Stefano Stabellini
2013-05-30 16:46 ` Andreas Färber [this message]
2013-05-30 16:46 ` Andreas Färber
2013-05-27 18:17 ` [Qemu-devel] [PATCH 2/2] xen: use pc_init_pci instead of pc_init_pci_no_kvmclock Stefano Stabellini
2013-05-27 18:17 ` Stefano Stabellini
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=51A7827E.3050706@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=anthony.perard@citrix.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.