Displaying 20 results from an estimated 20000 matches similar to: "[PATCH 2/2] linux/x86: Disable all accesses to the IO-APIC pages"
2009 Jan 21
11
[PATCH] x86: change IO-APIC ack method default for single IO-APIC systems
Ever since 3.0.2 we''ve been carrying this patch in our products. Since
there was no indication that there would be anything wrong with the
''new'' IO-APIC ack method added back then, we finally decided to drop
this patch recently from SLE11, to find that the subsequent release
candidate failed to work on at least on system without using
"ioapic_ack=old". With
2011 Sep 21
0
[PATCH] x86: IO-APIC code has no dependency on PCI
The IRQ handling code requires pcidevs_lock to be held only for MSI
interrupts.
As the handling of which was now fully moved into msi.c (i.e. while
applying fine without, the patch needs to be applied after the one
titled "x86: split MSI IRQ chip"), io_apic.c now also doesn''t need to
include PCI headers anymore.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
---
2013 Oct 30
1
[PATCH] x86/ACPI/x2APIC: guard against out of range ACPI or APIC IDs
Other than for the legacy APIC, the x2APIC MADT entries have valid
ranges possibly extending beyond what our internal arrays can handle,
and hence we need to guard ourselves against corrupting memory here.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/xen/arch/x86/acpi/boot.c
+++ b/xen/arch/x86/acpi/boot.c
@@ -97,7 +97,20 @@ acpi_parse_x2apic(struct acpi_subtable_h
2006 Apr 25
0
[PATCH] honor apic= despite MADT/MPS OEM match
While other aspects of the system configuration may still be controlled by the outcome of the table scan, if apic= was
given on the command line its effect should not be overridden here.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2013 May 02
5
[PATCH] x86: allow Dom0 read-only access to IO-APICs
There are BIOSes that want to map the IO-APIC MMIO region from some
ACPI method(s), and there is at least one BIOS flavor that wants to
use this mapping to clear an RTE''s mask bit. While we can''t allow the
latter, we can permit reads and simply drop write attempts, leveraging
the already existing infrastructure introduced for dealing with AMD
IOMMUs'' representation as
2013 Aug 28
7
[PATCH] x86/apic: remove DMI checks in bigsmp driver for obsolete systems
The DMI checks that force the use of the bigsmp APIC driver are for
systems that are no longer supported by Xen (32-bit x86).
Signed-off-by: Matt Wilson <msw@amazon.com>
Cc: Keir Fraser <keir@xen.org>
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
---
xen/arch/x86/genapic/bigsmp.c | 30 +-----------------------------
1 files changed, 1
2007 Feb 14
2
[PATCH 8/8] 2.6.17: scan DMI early
While shuffling quite a few things around, this gets us closer to native,
which clearly had a reason to do the DMI scan early.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Index: head-2007-02-08/arch/i386/mm/ioremap-xen.c
===================================================================
--- head-2007-02-08.orig/arch/i386/mm/ioremap-xen.c 2007-02-08 17:07:13.000000000 +0100
+++
2012 Sep 11
2
[PATCH RFC 5/8] ns16550: MMIO adjustments
On x86 ioremap() is not suitable here, set_fixmap() must be used
instead.
Also replace some literal numbers by their proper symbolic constants,
making the code easier to understand.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/xen/drivers/char/ns16550.c
+++ b/xen/drivers/char/ns16550.c
@@ -20,6 +20,9 @@
#include <xen/pci.h>
#include <xen/pci_regs.h>
#include
2011 Sep 23
0
[xen-unstable test] 9061: regressions - FAIL
flight 9061 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/9061/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-i386-rhel6hvm-amd 5 xen-boot fail REGR. vs. 8995
Tests which are failing intermittently (not blocking):
test-amd64-i386-pv 5 xen-boot fail pass in 9054
test-i386-i386-pv
2013 Aug 27
2
[PATCH] AMD IOMMU: add missing checks
For one we shouldn''t accept IVHD tables specifying IO-APIC IDs beyond
the limit we support (MAX_IO_APICS, currently 128).
And then we shouldn''t memset() a pointer allocation of which failed.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/xen/drivers/passthrough/amd/iommu_acpi.c
+++ b/xen/drivers/passthrough/amd/iommu_acpi.c
@@ -674,6 +674,13 @@ static u16 __init
2011 Mar 28
0
[xen-unstable test] 6714: regressions - FAIL
flight 6714 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/6714/
Regressions :-(
Tests which did not succeed and are blocking:
build-amd64-oldkern 4 xen-build fail REGR. vs. 6658
build-amd64 4 xen-build fail REGR. vs. 6658
build-i386-oldkern 4 xen-build fail REGR. vs. 6658
2008 Oct 17
6
[PATCH, RFC] i386: highmem access assistance hypercalls
While looking at the origin of very frequently executed hypercalls I
realized that the high page accessor functions in Linux would be good
candidates to handle in the hypervisor - clearing or copying to/from
a high page is a pretty frequent operation (provided there''s enough
memory in the domain). While prior to the first submission I only
measured kernel builds (where the results are not
2008 Jul 24
2
[RFC] i386 highmem assist hypercalls
While looking at the origin of very frequently executed hypercalls (as
usual, kernel builds are what''s being measured), I realized that the high
page accessor functions in Linux would be good candidates to handle
in the hypervisor - clearing or copying to/from a high page is a pretty
frequent operation (provided there''s enough memory). However, the
measured results
2011 Nov 11
4
[PATCH] x86: clean up __io_apic_eoi()
Irrespective of the IO-APIC vector sharing suppression patch just sent
the logic in this function needs to iterate over all RTEs, since
multiple pins within an IO-APIC may still use the same vector. This is
due to the irq_2_pin[] mapping not necessarily being 1:1.
Consequently we should remove the commented out code as well as the
respective comments provisioned for the point in time when vector
2011 Jul 17
0
[xen-4.1-testing test] 8111: regressions - FAIL
flight 8111 xen-4.1-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8111/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-i386-rhel6hvm-amd 12 guest-localmigrate/x10 fail in 8104 REGR. vs. 8020
Tests which are failing intermittently (not blocking):
test-amd64-i386-rhel6hvm-amd 11 guest-localmigrate.2 fail pass in 8104
2012 Oct 24
5
[PATCH v3] IOMMU: keep disabled until iommu_setup() is called
The iommu is enabled by default when xen is booting and later disabled
in iommu_setup() when no iommu is present.
But under some circumstances iommu code can be called before
iommu_setup() is processed. If there is no iommu available xen crashes.
This can happen for example when panic(...) is called as introduced
with the patch "x86-64: detect processors subject to AMD erratum #121
and
2013 Jul 09
6
4.3 regression in booting on a particular platform
Jan,
I was given a machine to diagnose a boot problem on xen 4.3, that used
to work on 4.2, and have bisected to the following changeset:
commit d0d4635d034f202bb401a6efa3ba61530f3854ab
Author: Jan Beulich <jbeulich@suse.com>
Date: Thu Nov 22 10:47:58 2012 +0100
implement vmap()
... and use it as basis for a proper ioremap() on x86.
Signed-off-by: Jan Beulich
2010 Feb 25
0
[Xen-devel] Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686) / bugfix patches
Hello,
The email (thread) below from xen-devel mailinglist indicates the changesets
that should fix the bug that causes the lenny 2.6.26 xen kernel to crash on
newer xen hypervisors.
The workaround for this bug has been to use pci=nomsi on the dom0 kernel cmdline,
but it would be better to apply the actual fix to the xen kernel in lenny.
More information on xen-devel (archives).
-- Pasi
2006 Jun 23
1
[PATCH] x86: fix microcode updater
This patch syncs up the microcode driver with linux 2.6.17 and adds on top of this enhancements (yet to be submitted to
lkml) to prevent the driver from disabling interrupts for long periods of time. This is done by IPI-ing all remote CPUs
sequentially rather than at once so they don''t all race for the same spin lock(s). Additionally, redundant updates on
multiple siblings of the same
2013 Sep 23
1
[PATCH v2] xen/x86: add a comment regarding how to get the VCPU ID on HVM
Add a note to the public headers regarding how to get the VCPU ID for
HVM guests (on x86).
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Matt Wilson <msw@amazon.com>
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Matt Wilson <msw@amazon.com>
---
This is what Linux PVHVM