qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	QEMU-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] e1000: Handle IO Port.
Date: Thu, 30 Jun 2011 19:45:04 +0100	[thread overview]
Message-ID: <BANLkTimXNcUj2RuZSQ5C4y6r80qQeeQHdA@mail.gmail.com> (raw)
In-Reply-To: <4E096B5F.7040309@redhat.com>

On Tue, Jun 28, 2011 at 06:49, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 06/27/2011 08:07 PM, Peter Maydell wrote:
>>
>> >  +    int ioport_base;
>> >  +    uint32_t ioport_reg[2];
>>
>> I think ioport_reg[] needs to go in the VMStateDescription as well.
>> I don't know enough about the PCI subsystem to know whether that's
>> also true of ioport_base or whether the the map function is called
>> again on a vmload.
>
> ioport_reg[1] is never written nor read, so this can be changed to a single
> uint32_t ioport_addr.  Since it will be almost always 0 (either because it
> was never written, or because E1000_CTRL == 0), a subsection is useful to
> have.

Indeed, I will remove ioport_reg[1] and ioport_addr.

Thanks,

-- 
Anthony PERARD

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 16:34 [Qemu-devel] [PATCH] e1000: Handle IO Port Anthony PERARD
2011-06-27 18:07 ` Peter Maydell
2011-06-28  5:49   ` Paolo Bonzini
2011-06-30 18:45     ` Anthony PERARD [this message]
2011-06-30 18:37   ` Anthony PERARD
  -- strict thread matches above, loose matches on Subject: below --
2010-10-12 13:58 anthony.perard

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=BANLkTimXNcUj2RuZSQ5C4y6r80qQeeQHdA@mail.gmail.com \
    --to=anthony.perard@citrix.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).