qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH rebased for-1.8] i386: pc: align gpa<->hpa on 1GB boundary (v6)
Date: Wed, 11 Dec 2013 01:17:50 +0200	[thread overview]
Message-ID: <20131210231750.GA27967@redhat.com> (raw)
In-Reply-To: <52A7928C.80005@redhat.com>

On Tue, Dec 10, 2013 at 11:15:40PM +0100, Laszlo Ersek wrote:
> On 12/10/13 23:13, Laszlo Ersek wrote:
> 
> > Please let OVMF know about the big MMIO range (the "split" you mention)
> > - that is going to be advertised via ACPI to the OS,
> > - in an easy to parse format over fw_cfg.
> 
> Anyway just ignore me this time. I test OVMF regularly on fresh qemu
> builds and if something breaks I'll complain. (NB the current status
> *is* broken, I just haven't been complaining recently because I keep
> rebasing Gerd's patch.)
> 
> Thanks
> Laszlo

I'd like to merge Gerd's patch, and a similar patch for q35.
For q35 we need to get rid of MCH_HOST_BRIDGE_PCIEXBAR_DEFAULT.

However, I think we have to limit this change to pc-2.0 and newer:
qemu 1.8 still has the "pci hole" concept, so guest can't put
devices outside the specific ranges.

Anyone plans to look into this?

-- 
MST

  reply	other threads:[~2013-12-10 23:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 17:43 [Qemu-devel] [PATCH rebased for-1.8] i386: pc: align gpa<->hpa on 1GB boundary (v6) Paolo Bonzini
2013-11-25 20:58 ` Laszlo Ersek
2013-11-25 21:05 ` Michael S. Tsirkin
2013-11-25 23:09   ` Marcelo Tosatti
2013-11-26  9:04   ` Paolo Bonzini
2013-11-28 10:26 ` Michael S. Tsirkin
2013-12-10 13:18   ` Paolo Bonzini
2013-12-10 14:53     ` Gerd Hoffmann
2013-12-10 14:58       ` Paolo Bonzini
2013-12-10 15:36         ` Gerd Hoffmann
2013-12-10 15:47       ` Laszlo Ersek
2013-12-10 15:53         ` Gerd Hoffmann
2013-12-10 17:46           ` Laszlo Ersek
2013-12-10 17:48             ` Paolo Bonzini
2013-12-10 21:00             ` Michael S. Tsirkin
2013-12-10 22:13               ` Laszlo Ersek
2013-12-10 22:15                 ` Laszlo Ersek
2013-12-10 23:17                   ` Michael S. Tsirkin [this message]
2013-12-11  8:00                     ` Gerd Hoffmann
2013-12-10 15:05     ` Marcelo Tosatti
2013-12-10 17:21       ` Marcelo Tosatti
2013-12-10 21:02         ` Michael S. Tsirkin
2013-12-11 13:41           ` Marcelo Tosatti
2013-12-11 14:20             ` Michael S. Tsirkin
2013-12-11 14:45               ` Paolo Bonzini
2013-12-11 15:39                 ` Michael S. Tsirkin
2013-12-11 15:41                   ` Paolo Bonzini
2013-12-11 15:51                     ` Michael S. Tsirkin
2013-12-11 15:45                 ` Igor Mammedov
2013-12-11 15:56                   ` Paolo Bonzini
2013-12-11 17:26                 ` Marcelo Tosatti
2013-12-10 16:52     ` 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=20131210231750.GA27967@redhat.com \
    --to=mst@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mtosatti@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).