From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 1.1 1/4] xen: do not initialize the interval timer and PCSPK emulator
Date: Mon, 14 May 2012 11:38:34 -0500 [thread overview]
Message-ID: <4FB1350A.6020106@codemonkey.ws> (raw)
In-Reply-To: <1336567456-20202-1-git-send-email-stefano.stabellini@eu.citrix.com>
On 05/09/2012 07:44 AM, Stefano Stabellini wrote:
> PIT and PCSPK are emulated by the hypervisor so we don't need to emulate
> them in Qemu: this patch prevents Qemu from waking up needlessly at
> PIT_FREQ on Xen.
>
> Signed-off-by: Stefano Stabellini<stefano.stabellini@eu.citrix.com>
> ---
> hw/pc.c | 23 +++++++++++++----------
> 1 files changed, 13 insertions(+), 10 deletions(-)
>
> diff --git a/hw/pc.c b/hw/pc.c
> index 4d34a33..c52caf6 100644
> --- a/hw/pc.c
> +++ b/hw/pc.c
> @@ -47,6 +47,7 @@
> #include "ui/qemu-spice.h"
> #include "memory.h"
> #include "exec-memory.h"
> +#include "arch_init.h"
>
> /* output Bochs bios info messages */
> //#define DEBUG_BIOS
> @@ -1097,7 +1098,7 @@ void pc_basic_device_init(ISABus *isa_bus, qemu_irq *gsi,
> qemu_irq pit_alt_irq = NULL;
> qemu_irq rtc_irq = NULL;
> qemu_irq *a20_line;
> - ISADevice *i8042, *port92, *vmmouse, *pit;
> + ISADevice *i8042, *port92, *vmmouse, *pit = NULL;
> qemu_irq *cpu_exit_irq;
>
> register_ioport_write(0x80, 1, 1, ioport80_write, NULL);
> @@ -1126,16 +1127,18 @@ void pc_basic_device_init(ISABus *isa_bus, qemu_irq *gsi,
>
> qemu_register_boot_set(pc_boot_set, *rtc_state);
>
> - if (kvm_irqchip_in_kernel()) {
> - pit = kvm_pit_init(isa_bus, 0x40);
> - } else {
> - pit = pit_init(isa_bus, 0x40, pit_isa_irq, pit_alt_irq);
> - }
> - if (hpet) {
> - /* connect PIT to output control line of the HPET */
> - qdev_connect_gpio_out(hpet, 0, qdev_get_gpio_in(&pit->qdev, 0));
> + if (!xen_available()) {
Shouldn't this be xen_enabled()?
Regards,
Anthony Liguori
> + if (kvm_irqchip_in_kernel()) {
> + pit = kvm_pit_init(isa_bus, 0x40);
> + } else {
> + pit = pit_init(isa_bus, 0x40, pit_isa_irq, pit_alt_irq);
> + }
> + if (hpet) {
> + /* connect PIT to output control line of the HPET */
> + qdev_connect_gpio_out(hpet, 0, qdev_get_gpio_in(&pit->qdev, 0));
> + }
> + pcspk_init(isa_bus, pit);
> }
> - pcspk_init(isa_bus, pit);
>
> for(i = 0; i< MAX_SERIAL_PORTS; i++) {
> if (serial_hds[i]) {
next prev parent reply other threads:[~2012-05-14 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 12:43 [PATCH 1.1] rebase xen patches Stefano Stabellini
2012-05-09 12:44 ` [PATCH 1.1 1/4] xen: do not initialize the interval timer and PCSPK emulator Stefano Stabellini
2012-05-14 16:38 ` Anthony Liguori [this message]
2012-05-14 17:00 ` Stefano Stabellini
2012-05-09 12:44 ` [PATCH 1.1 2/4] xen: disable rtc_clock Stefano Stabellini
2012-05-09 12:44 ` [PATCH 1.1 3/4] xen_disk: remove syncwrite option Stefano Stabellini
2012-05-09 12:44 ` [PATCH 1.1 4/4] xen_disk: use bdrv_aio_flush instead of bdrv_flush 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=4FB1350A.6020106@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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 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).