From: Gerd Hoffmann <kraxel@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org
Cc: mst@redhat.com, pbonzini@redhat.com, ehabkost@redhat.com,
Igor Mammedov <imammedo@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/pci-host: Fix x86 Host Bridges 64bit PCI hole
Date: Mon, 23 Oct 2017 11:16:16 +0200 [thread overview]
Message-ID: <1508750176.16488.6.camel@redhat.com> (raw)
In-Reply-To: <083108b4-6300-6302-d8c8-108fc6ae07fb@redhat.com>
On Mon, 2017-10-23 at 11:46 +0300, Marcel Apfelbaum wrote:
> On 23/10/2017 8:45, Gerd Hoffmann wrote:
> > Hi,
> >
> > > The guest will still run with 40 bits physical!
> > > (judging the code anyway, I hope I am wrong)
> > >
> > > Then, the stakes are not so big, the Guest kernel will disregard
> > > the 64bit hole since is not CPU addressable and go on.
> >
> > But then there is no working 64bit hole for hotplug ...
> >
>
> Hosts with old CPUs are not fit for modern PCIe devices
> having large BARs anyway, no 64bit hole in this case would
> be OK, I think.
Well, my workstation which has only 39 bits physical is kaby lake.
If you classify this as "old cpu", what is a new cpu then?
cheers,
Gerd
next prev parent reply other threads:[~2017-10-23 9:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 9:58 [Qemu-devel] [PATCH] hw/pci-host: Fix x86 Host Bridges 64bit PCI hole Marcel Apfelbaum
2017-10-18 10:45 ` Igor Mammedov
2017-10-18 10:57 ` Marcel Apfelbaum
2017-10-18 11:40 ` Laszlo Ersek
2017-10-19 9:30 ` Marcel Apfelbaum
2017-10-19 10:41 ` Laszlo Ersek
2017-10-19 11:29 ` Marcel Apfelbaum
2017-10-19 11:52 ` Laszlo Ersek
2017-10-19 13:03 ` Gerd Hoffmann
2017-10-19 13:34 ` Marcel Apfelbaum
2017-10-20 6:55 ` Gerd Hoffmann
2017-10-20 9:32 ` Laszlo Ersek
2017-10-20 10:59 ` Gerd Hoffmann
2017-10-20 14:06 ` Marcel Apfelbaum
2017-10-20 13:47 ` Marcel Apfelbaum
2017-10-23 5:45 ` Gerd Hoffmann
2017-10-23 8:46 ` Marcel Apfelbaum
2017-10-23 9:16 ` Gerd Hoffmann [this message]
2017-10-23 9:35 ` Marcel Apfelbaum
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=1508750176.16488.6.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@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).