qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hpet: check no_hpet when adding fw_cfg entry.
Date: Mon, 13 Sep 2010 21:37:40 +0200	[thread overview]
Message-ID: <20100913193740.GD13951@redhat.com> (raw)
In-Reply-To: <1283774484-11575-1-git-send-email-kraxel@redhat.com>

On Mon, Sep 06, 2010 at 02:01:24PM +0200, Gerd Hoffmann wrote:
> We should only pass the hpet config entry in case we actually
> create a hpet device.
> 
No we should pass it always. If no hpets are present hpet_cfg will have
appropriate info.


> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
>  hw/pc.c |    6 ++++--
>  1 files changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/pc.c b/hw/pc.c
> index 0c31db1..c96f1fc 100644
> --- a/hw/pc.c
> +++ b/hw/pc.c
> @@ -517,8 +517,10 @@ static void *bochs_bios_init(void)
>      fw_cfg_add_bytes(fw_cfg, FW_CFG_E820_TABLE, (uint8_t *)&e820_table,
>                       sizeof(struct e820_table));
>  
> -    fw_cfg_add_bytes(fw_cfg, FW_CFG_HPET, (uint8_t *)&hpet_cfg,
> -                     sizeof(struct hpet_fw_config));
> +    if (!no_hpet) {
> +        fw_cfg_add_bytes(fw_cfg, FW_CFG_HPET, (uint8_t *)&hpet_cfg,
> +                         sizeof(struct hpet_fw_config));
> +    }
>      /* allocate memory for the NUMA channel: one (64bit) word for the number
>       * of nodes, one word for each VCPU->node and one word for each node to
>       * hold the amount of memory.
> -- 
> 1.7.1
> 

--
			Gleb.

      reply	other threads:[~2010-09-13 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 12:01 [Qemu-devel] [PATCH] hpet: check no_hpet when adding fw_cfg entry Gerd Hoffmann
2010-09-13 19:37 ` Gleb Natapov [this message]

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=20100913193740.GD13951@redhat.com \
    --to=gleb@redhat.com \
    --cc=kraxel@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).