All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] vga: Fix type of map_addr/end.
Date: Tue, 14 Jun 2011 20:14:10 +0200	[thread overview]
Message-ID: <4DF7A4F2.9000708@siemens.com> (raw)
In-Reply-To: <1308073492-24789-1-git-send-email-rth@twiddle.net>

On 2011-06-14 19:44, Richard Henderson wrote:
> These addresses have been passed through pci_to_cpu_addr,
> and thus need to be full target_phys_addr_t.

Basically correct, but you also need to change the types of
lfb_addr/end, no?

> 
> Signed-off-by: Richard Henderson <rth@twiddle.net>
> Cc: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  hw/vga_int.h |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> Jan's recent patch series reminded me that I found a related
> problem in my alpha-softmmu port this past weekend.  Note that
> the slight re-ordering of the members avoids extra padding in
> the structure due to alignment.

Yeah, and I just noticed a harmless mistyping in my patches while
thinking about your type changes.

Jan

> 
> 
> diff --git a/hw/vga_int.h b/hw/vga_int.h
> index d2811bd..b65775b 100644
> --- a/hw/vga_int.h
> +++ b/hw/vga_int.h
> @@ -109,9 +109,9 @@ typedef struct VGACommonState {
>      uint32_t vram_size;
>      uint32_t lfb_addr;
>      uint32_t lfb_end;
> -    uint32_t map_addr;
> -    uint32_t map_end;
>      uint32_t lfb_vram_mapped; /* whether 0xa0000 is mapped as ram */
> +    target_phys_addr_t map_addr;
> +    target_phys_addr_t map_end;
>      uint32_t latch;
>      uint8_t sr_index;
>      uint8_t sr[256];

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-06-14 18:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 17:44 [Qemu-devel] [PATCH] vga: Fix type of map_addr/end Richard Henderson
2011-06-14 18:14 ` Jan Kiszka [this message]
2011-06-14 18:41   ` Richard Henderson

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=4DF7A4F2.9000708@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.