From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Gal Hammer <ghammer@redhat.com>,
imammedo@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V15 4/5] i386: add a Virtual Machine Generation ID device
Date: Thu, 28 May 2015 15:24:18 +0200 [thread overview]
Message-ID: <20150528152225-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <55671184.30300@redhat.com>
On Thu, May 28, 2015 at 03:00:52PM +0200, Paolo Bonzini wrote:
>
>
> On 28/05/2015 14:21, Michael S. Tsirkin wrote:
> > > And the way I can fix it would be...? Is there another memory region I can
> > > use?
> > >
> > > Thanks,
> > >
> > > Gal.
> >
> > I think we hammered out an interesting alternative off-list: get hold of
> > some AddressRegionNVS memory and copy data from MMIO or port io over
> > there when you get an interrupt.
>
> That doesn't work because there's no way to get the base address of a
> DataTableRegion.
>
> You could use a linker ADD_POINTER command, but it wouldn't work for
> UEFI.
Hmm why not? UEFI runs these as well.
> So I think it's best to just stay with this one. If we do find
> something better we can always change it later.
>
> Paolo
next prev parent reply other threads:[~2015-05-28 13:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 11:19 [Qemu-devel] [PATCH V15 0/5] Virtual Machine Generation ID Gal Hammer
2015-04-27 11:19 ` [Qemu-devel] [PATCH V15 1/5] docs: vm generation id device's description Gal Hammer
2015-04-27 13:42 ` Michael S. Tsirkin
2015-04-27 13:55 ` Michael S. Tsirkin
2015-04-28 14:20 ` Gal Hammer
2015-04-27 14:56 ` Eric Blake
2015-04-28 14:38 ` Gal Hammer
2015-04-27 11:19 ` [Qemu-devel] [PATCH V15 2/5] acpi: add a vm_generation_id_changed method Gal Hammer
2015-04-27 14:57 ` Eric Blake
2015-04-27 11:19 ` [Qemu-devel] [PATCH V15 3/5] aml: implement a 32-bit fixed memory range descriptor Gal Hammer
2015-04-27 11:19 ` [Qemu-devel] [PATCH V15 4/5] i386: add a Virtual Machine Generation ID device Gal Hammer
2015-04-27 13:38 ` Michael S. Tsirkin
2015-04-29 12:46 ` Gal Hammer
2015-04-27 14:59 ` Eric Blake
2015-05-28 10:25 ` Paolo Bonzini
2015-05-28 11:49 ` Michael S. Tsirkin
2015-05-28 11:59 ` Gal Hammer
2015-05-28 12:21 ` Michael S. Tsirkin
2015-05-28 13:00 ` Paolo Bonzini
2015-05-28 13:24 ` Michael S. Tsirkin [this message]
2015-05-28 13:35 ` Paolo Bonzini
2015-05-29 11:46 ` Igor Mammedov
2015-06-03 16:32 ` Michael S. Tsirkin
2015-06-03 16:37 ` Paolo Bonzini
2015-06-08 13:42 ` Gal Hammer
2015-06-08 13:43 ` Paolo Bonzini
2015-06-08 13:52 ` Gal Hammer
2015-06-08 13:55 ` Paolo Bonzini
2015-06-08 13:58 ` Daniel P. Berrange
2015-06-08 14:05 ` Gal Hammer
2015-06-08 15:01 ` Michael S. Tsirkin
2015-06-08 15:17 ` Paolo Bonzini
2015-06-08 15:22 ` Michael S. Tsirkin
2015-06-08 15:28 ` Gal Hammer
2015-06-08 15:32 ` Michael S. Tsirkin
2015-06-08 15:33 ` Paolo Bonzini
2015-06-08 15:41 ` Michael S. Tsirkin
2015-06-08 15:43 ` Paolo Bonzini
2015-06-08 14:00 ` Gal Hammer
2015-06-08 13:59 ` Paolo Bonzini
2015-04-27 11:19 ` [Qemu-devel] [PATCH V15 5/5] tests: add a unit test for the vmgenid device Gal Hammer
2015-04-27 15:01 ` Eric Blake
2015-04-27 16:17 ` Michael S. Tsirkin
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=20150528152225-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=ghammer@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@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).