Package Details: linux-vfio-docs 4.20.1.arch1-1

Git Clone URL: https://aur.archlinux.org/linux-vfio.git (read-only)
Package Base: linux-vfio
Description: Kernel hackers manual - HTML documentation that comes with the Linux-vfio kernel
Upstream URL: https://git.archlinux.org/linux.git/log/?h=v4.20.1-arch1
Keywords: acs arbiter assignment gpu i915 kvm override passthrough pci qemu vfio vga
Licenses: GPL2
Submitter: zman0900
Maintainer: zman0900 (markzz)
Last Packager: markzz
Votes: 50
Popularity: 0.953770
First Submitted: 2015-01-30 06:41
Last Updated: 2019-01-14 15:53

Pinned Comments

markzz commented on 2017-12-14 06:10

(4.14.5+) Because Arch itself has dropped i686 support, I have removed i686 from the PKGBUILD and there is no config file either.

electricprism commented on 2016-01-04 04:30

Requires importing GPG Keys to build

# Linus Torvalds
gpg --recv-keys 79BE3E4300411886

# Greg Kroah-Hartman (Linux kernel stable release signing key)
gpg --recv-keys 38DBBDC86092693E

Latest Comments

1 2 3 4 5 6 ... Next › Last »

NeoTheFox commented on 2018-12-12 20:10

The latest version (4.19.8-arch1-1-vfio) has build error due to patch:

drivers/pci/quirks.c:4617:28: error: ‘pci_acs_overrides’ undeclared here (not in a function); did you mean ‘pcie_acs_overrides’? { PCI_ANY_ID, PCI_ANY_ID, pci_acs_overrides }, ^~~~~~~~~~~~~~~~~ pcie_acs_overrides

markzz commented on 2018-12-12 16:30

I have pushed something that the patches apply, but I haven't tested the package itself.

markzz commented on 2018-12-12 14:09

whight: The vga arbiter patch does not apply in 4.19.x.

Applying: i915: Add module option to support VGA arbiter on HD devices (4.17)
error: patch failed: drivers/gpu/drm/i915/i915_params.c:133
error: drivers/gpu/drm/i915/i915_params.c: patch does not apply
error: patch failed: drivers/gpu/drm/i915/i915_params.h:58
error: drivers/gpu/drm/i915/i915_params.h: patch does not apply
error: patch failed: drivers/gpu/drm/i915/intel_display.c:15402
error: drivers/gpu/drm/i915/intel_display.c: patch does not apply

whight commented on 2018-12-12 08:36

You shouldn't have any troubles using the patch in your sources for 4.19.8. Built and tested it myself with linux from the core repo. If you'd like, I can help keep this maintained.

markzz commented on 2018-12-05 14:00

archqemu: I try to keep up to date with regards to whatever version is in [core]. The problem is, on version releases (e.g. 4.14 -> 4.15), I often have to rewrite the patches (this isn't normally a problem on patch releases like 4.16.7 -> 4.16.8). Because I'm both a full time student and work full time as a software engineer, I am sometimes unable to set aside enough time to update the patches and I get to it when I can. The semester is almost over at the time of this comment, so I should be able to set aside time for sure then, if not sooner.

archqemu commented on 2018-12-05 13:51

okay cool, thanks for your quick reply!

I was just curious if there is any systematic release schedule related to the kernel releases.

markzz commented on 2018-12-05 10:14

archqemu: When it's done.

archqemu commented on 2018-12-05 10:07

When can we expect an update of this package?

jmandawg commented on 2018-10-29 17:51

Awesome thanks markzz, I didn't know this, i'm still a bit of a noob (switched from debian) i'm going to try this for the next kernel update. Thanks again.

markzz commented on 2018-10-29 14:44

jmandawg: This is because when you boot this kernel without building the dkms module for it, it will of course not work. Because this is information any user of DKMS should know about, I don't see a reason to pin a comment about that.

I think this is something that you should read what the wiki states on DKMS because it actually lays out the steps to make sure the module is built for your kernel in use and does not require a reinstall of the nvidia-dkms package.

https://wiki.archlinux.org/index.php/Dynamic_Kernel_Module_Support