<div dir="ltr">So I checked back on my old config- forcing X2APIC helped me on 3.x kernels only, I have not observed any effect on 4.x kernels though, so this can most-likely be disregarded for Arch. </div><br><div class="gmail_quote"><div dir="ltr">On Tue, May 24, 2016 at 11:45 AM Spam House <<a href="mailto:kthxplzdie@gmail.com">kthxplzdie@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey Colin,<div><br></div><div>I am curious about this as well. Please provide more information on your setup regarding X2APIC.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 21, 2016 at 10:42 AM, Colin Godsey <span dir="ltr"><<a href="mailto:crgodsey@gmail.com" target="_blank">crgodsey@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Windows 10 forcing X2APIC: <a href="https://support.microsoft.com/en-us/kb/2303458" target="_blank">https://support.microsoft.com/en-us/kb/2303458</a><div><br></div><div>This helped a bunch for me at least on 4.4- I think there was some confusion on the correct way to signal the guest on what APIC to use, forcing this gave me much better %sys times. AFAIK it can also still be used with hyper-v APIC because that’s just the EOI para-virtualization. </div></div><br><div class="gmail_quote"><div><div><div dir="ltr">On Fri, May 20, 2016 at 2:28 PM Alex Williamson <<a href="mailto:alex.l.williamson@gmail.com" target="_blank">alex.l.williamson@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, May 20, 2016 at 11:38 AM, Nicolas Roy-Renaud <span dir="ltr"><<a href="mailto:nicolas.roy-renaud.1@ens.etsmtl.ca" target="_blank">nicolas.roy-renaud.1@ens.etsmtl.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Did you have any issues with efifb or some other driver grabbing
the gard before vfio-pci? What are your IOMMU groups like, which
chard is your boot_vga, what script or method do you use to get
vfio-pci to bind with your card, what's your kernel command line
and what modules are included in your initramfs?</p>
<p>I've struggled with getting my primary GPU to work correctly for
a passthrough like this, and I ended up switching it up with the
secondary because I simply couldn't get it to work properly (I'd
keep getting something about "<code>Invalid ROM contents</code>")
and I couldn't see my boot logs until the host driver finished
loading. It's really inconvenient now becuase my motherboard is
designed so that having a full-size GPU in the second PCIe slot
blocks 4 SATA ports out of 6, so I need to have L-shaped cables in
a bunch of places to make everything work properly.</p></div></blockquote><div><br></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>The boot VGA ROM is handled differently from other PCI ROMs in Linux, when you read it you're actually reading a shadow copy of it placed at 0xc0000, which has its roots back in the original IBM PC history. Execution of the VGA ROM is allowed to modify this copy of the ROM image in memory. Thus you're really not getting a pristine copy of the device ROM and it can often lead to these invalid ROM contents messages. I wish we provided raw access to the PCI option ROM in these cases as well. For now, if you do have these sorts of invalid ROM messages, I would suggest that you at least boot with the card as secondary, dump the ROM, then use that collected image with the romfile= option rather than use the shadow copy. I had to add some code to vfio to fix device IDs and checksums for IGD assignment because of this, I don't know if there's any standard fixup we can do for other vendors. Thanks,</div><div><br></div><div>Alex</div></div></div></div></div></div><span>
_______________________________________________<br>
vfio-users mailing list<br>
<a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a><br>
</span></blockquote></div>
<br>_______________________________________________<br>
vfio-users mailing list<br>
<a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a><br>
<br></blockquote></div><br></div>
</blockquote></div>