Re: [PATCH 1/9] pci-assign: Optionally enable 64bit BARs in guest

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/31/2012 03:21 PM, Jan Kiszka wrote:
> On 2012-01-31 14:10, Avi Kivity wrote:
> > On 01/31/2012 02:57 PM, Jan Kiszka wrote:
> >>>>> Seems fine, but do we really need the option?  If it doesn't work we
> >>>>> should treat it as an ordinary but and fix it.
> >>>>
> >>>> So far it's against the architecture of the emulated system: our current
> >>>> chipset predates 64 bit PCI.
> >>>>
> >>>
> >>> Then it should be enabled/disabled at the chipset level.
> >>
> >> Makes me wonder if we already do some filtering if the device supports
> >> 64 bit but the next bridge does not.
> >>
> > 
> > Our 440fx does support 64-bit bars, so the question doesn't arise for
> > x86.  Instead we violate the spec.
>
> If you mean by "our" the 440fx-qemu, not the real 440fx. That one does
> not even support >1GB RAM.

Yes, that's what I meant.  It also supports pci hotplug, more slots, cpu
hotplug, etc.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux