On Wed, 2015-08-05 at 15:23 +0200, Eric Auger wrote:
> Hi Alex,
> On 07/16/2015 11:26 PM, Alex Williamson wrote:
> > When a physical I/O device is assigned to a virtual machine through
> > facilities like VFIO and KVM, the interrupt for the device generally
> > bounces through the host system
On Wed, Aug 05, 2015 at 08:31:27PM +0530, raghu MG wrote:
> Hi Andrew,
>
> The issue I found was irq_alloc_descs is called twice
> 1st time inside mvebu_gpio_probe & 2nd time inside irq_domain_add_simple.
So i'm somewhat confused. I just tested on my Kirkwood and 370
platforms, and an Armada
On Wed, Aug 05, 2015 at 09:43:00PM +0530, Chandra S Gorentla wrote:
> Added 'void' keyword in the paranthesis of function definitions, when
> there are no arguments to the functions. This fixes the checkpatch.pl
> error - "Bad function definition 'function()' should probably be
> function(void)".
On Wed, Aug 05, 2015 at 10:44:24AM +0200, Ingo Molnar wrote:
>
> * Shaohua Li wrote:
>
> > On Sun, Aug 02, 2015 at 09:41:08PM +0200, Thomas Gleixner wrote:
> > > On Sun, 2 Aug 2015, Shaohua Li wrote:
> > >
> > > > On Sat, Aug 01, 2015 at 12:10:41PM +0200, Thomas Gleixner wrote:
> > > > > On
On Wed 2015-08-05 17:11:48, Jiri Slaby wrote:
> On 08/05/2015, 01:52 PM, Jiri Slaby wrote:
> >> Yes, I see:
> >> sdhci-pci :02:00.0: swiotlb buffer is full (sz: 65536 bytes)
> >> after some time. The driver falls back to non-DMA transfers after that.
> >> It also generates a warning about
On Wed, Aug 05, 2015 at 09:08:32AM -0700, Alexei Starovoitov wrote:
> On 8/5/15 6:53 AM, Peter Zijlstra wrote:
> >+/*
> >+ * If the event is currently on this CPU, its either a per-task event,
> >+ * or local to this CPU. Furthermore it means its ACTIVE (otherwise
> >+ * oncpu ==
Hi!
> Add a document describing the process of adding a new system call,
> including the need for a flags argument for future compatibility, and
> covering 32-bit/64-bit concerns (albeit in an x86-centric way).
>
> Signed-off-by: David Drysdale
> Reviewed-by: Michael Kerrisk
> Reviewed-by:
On Wed, 2015-08-05 at 09:37 +0100, Javi Merino wrote:
> On Tue, Aug 04, 2015 at 05:39:21PM +0100, Dmitry Torokhov wrote:
> > As it currently stands the power allocator governor can not handle
> > thermal zones that are not specifically crafted and therefore can not be
> > used as a default
Added 'void' keyword in the paranthesis of function definitions, when
there are no arguments to the functions. This fixes the checkpatch.pl
error - "Bad function definition 'function()' should probably be
function(void)".
---
drivers/staging/wilc1000/linux_mon.c | 2 +-
The character ' ' is removed after the character '('. This fixes the
checkpatch.pl error - "space prohibited after that open
parenthesis '('".
---
drivers/staging/wilc1000/wilc_wfi_cfgoperations.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Moved the opening brace of code blocks to the previous lines. This
fixes the checkpatch.pl error - "that open brace { should be on the
previous line".
---
drivers/staging/wilc1000/wilc_wfi_cfgoperations.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git
On Wed, 05 Aug, at 05:10:00PM, Matt Fleming wrote:
> On Wed, 05 Aug, at 08:58:52AM, Zhang, Jonathan Zhixiong wrote:
> >
> > Yes, absolutely. It has been in my mind, sorry I was tied up in the last
> > few days. I wonder what I may missed, I certainly do x86 build test with
> > versions of the
On Thu, Jul 30, 2015 at 10:53:54AM -0700, Bjorn Andersson wrote:
> From: Courtney Cavin
>
> Reviewed-by: Andy Gross
> Signed-off-by: Courtney Cavin
> Signed-off-by: Bjorn Andersson
> ---
>
> Changes since v1:
> - Corrected authorship
>
> drivers/spmi/spmi-pmic-arb.c | 17 +
v2 - Resending as v1 patch series did not apply cleanly.
These patches fixes a few style errors reported by checkpatch.pl.
PATCH 3/3 should be applied after PATCH 2/3.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
On Mon 2015-07-27 09:12:53, Markus Pargmann wrote:
> Signed-off-by: Markus Pargmann
Acked-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line
Fix typos and change "relative state of charge" to "state of charge" as not
all supported devices use relative state of charge.
Signed-off-by: Andrew F. Davis
Acked-by: Pali Rohár
Acked-by: Pavel Machek
---
drivers/power/bq27xxx_battery.c | 28 ++--
1 file changed, 14
The MODULE_DEVICE_TABLE macro automatically adds all needed
i2c MODULE_ALIASes so remove the extra MODULE_ALIAS.
Signed-off-by: Andrew F. Davis
Acked-by: Pali Rohár
---
drivers/power/bq27x00_battery.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/power/bq27x00_battery.c
Hello,
On Wed, Aug 05, 2015 at 01:22:57PM +0100, Matt Fleming wrote:
> I wager that this assertion is wrong. Having individual applications
> program their own cache mask is not going to be the most common
> scenario. Only in very specific situations would you trust an
> application to do that.
On 05/08/15 16:50, David Vrabel wrote:
> Also perhaps make it
>
> int xen_for_each_gfn(struct page *page,
> xen_gfn_fn_t fn, void *data);
gfn standing for Guest Frame Number right?
>>>
>>> Yes. This suggestion is just changing the name to make it
On Fri, Jul 24, 2015 at 02:45:56PM +0300, Alexander Shishkin wrote:
> @@ -3890,7 +3958,7 @@ perf_read(struct file *file, char __user *buf, size_t
> count, loff_t *ppos)
> ret = perf_read_hw(event, buf, count);
> perf_event_ctx_unlock(event, ctx);
>
> - return ret;
> +
On Wed, 05 Aug, at 08:58:52AM, Zhang, Jonathan Zhixiong wrote:
>
> Yes, absolutely. It has been in my mind, sorry I was tied up in the last
> few days. I wonder what I may missed, I certainly do x86 build test with
> versions of the patch set.
>
> I will try today and report back.
No problem.
Reorganize the logic checking battery health and add under temperature
condition checking.
Signed-off-by: Andrew F. Davis
Acked-by: Pali Rohár
Acked-by: Pavel Machek
---
drivers/power/bq27xxx_battery.c | 64 +++--
1 file changed, 42 insertions(+), 22
On 8/5/15 6:53 AM, Peter Zijlstra wrote:
+ /*
+* If the event is currently on this CPU, its either a per-task event,
+* or local to this CPU. Furthermore it means its ACTIVE (otherwise
+* oncpu == -1).
+*/
+ if (event->oncpu == smp_processor_id())
+
Add support for additional devices and register equivalent family devices
including the bq27010, bq27210, bq27500, bq27510, bq27520, bq27530,
bq27531, bq27541, bq27542, bq27546, bq27545, bq27441, bq27421, and the
bq27641.
To facilitate this process the register mapings have been moved to tables
This series adds support for several additional bq27xxx devices and
makes a few related fixes. v1 can be found here: [1] v2: [2]
Changes from v2:
- Fix alignment issue
- Fix commit message typo
- Use INVALID_REG_ADDR in register mappings
Changes from v1:
- Drop first four patches from
When initialized as a platform device the initializer must now specify
a device. An empty device name is no longer valid.
Signed-off-by: Andrew F. Davis
---
drivers/power/bq27xxx_battery.c | 9 ++---
drivers/w1/slaves/w1_bq27000.c| 1 +
include/linux/power/bq27xxx_battery.h |
Rename functions that are used by multiple devices. New devices
have been added and the function names and driver name are no longer
general enough for the functionality they provide.
Signed-off-by: Andrew F. Davis
Acked-by: Pali Rohár
---
MAINTAINERS|
A recursive lockdep warning occurs if you call regulator_set_voltage()
on a load switches that are modelled as regulators with a parent supply as
there is no nesting annotation for the rdev->mutex.
To avoid this warning, use the unlocked version of the get_voltage().
wiithout this patch kernel
On 8/5/15 3:15 AM, Peter Zijlstra wrote:
On Wed, Aug 05, 2015 at 12:04:25PM +0200, Peter Zijlstra wrote:
On Tue, Aug 04, 2015 at 08:58:15AM +, Kaixu Xia wrote:
+ event->ctx->task != current)
Strictly speaking we should hold rcu_read_lock around dereferencing
event->ctx (or
On 8/5/15 3:04 AM, Peter Zijlstra wrote:
>+ __perf_event_read(event);
>+ return perf_event_count(event);
>+}
Also, you probably want a WARN_ON(in_nmi()) there, this function is
_NOT_ NMI safe.
we check that very early on:
unsigned int trace_call_bpf(struct bpf_prog *prog, void *ctx)
{
This patchs improves perf evlist by adding the
dump of the branch_sample_bits. This is part
of perf_event_attr and is important to know
when sampling branches.
Patch is relative to tip.git
Signed-off-by: Stephane Eranian
--
diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
index
On 8/5/2015 2:21 AM, Matt Fleming wrote:
On Tue, 04 Aug, at 08:41:36AM, Zhang, Jonathan Zhixiong wrote:
On 8/3/2015 9:25 PM, Borislav Petkov wrote:
On Mon, Aug 03, 2015 at 05:23:54PM +0100, Matt Fleming wrote:
Rafael, Boris?
The ghes.c change looks fine I guess. The whole patchset makes
Check that the use of the user accessors for accessing kernel memory
succeed as expected after set_fs(get_ds()) is used to increases the
address limit, as used by the kernel to directly invoke system call code
with kernel pointers.
The tests are basically the same as the tests normally expected
On Fri, Jul 24, 2015 at 02:45:56PM +0300, Alexander Shishkin wrote:
> +static void perf_error_report_site(struct perf_event_attr *attr,
> +const struct perf_err_site *site)
> +{
> + void *buffer;
> +
> + if (!site || !extended_reporting_enabled(attr))
> +
These patches extend the test_user_copy test module to handle lots more
cases of user accessors which architectures can override separately, and
in particular those which are important for checking the MIPS Enhanced
Virtual Addressing (EVA) implementations, which need to handle
overlapping user
Add basic success/failure checking of copy_in_user() which copies data
from userspace to userspace (or kernel to kernel), and its unchecking
cousin __copy_in_user() which assumes that access_ok() has already been
used as appropriate.
The following cases are checked:
- __copy_in_user/copy_in_user
Add basic success/failure checking of __copy_to_user_inatomic() and
__copy_from_user_inatomic(). For testing purposes these are similar to
their non-atomic non-checking friends, so the new tests match those for
__copy_to_user() and __copy_from_user().
New tests:
- legitimate
On 05/08/15 15:30, Julien Grall wrote:
> Hi David,
>
> On 24/07/15 11:10, David Vrabel wrote:
>> On 24/07/15 10:54, Julien Grall wrote:
>>> On 24/07/15 10:31, David Vrabel wrote:
On 09/07/15 21:42, Julien Grall wrote:
> The Xen interface is always using 4KB page. This means that a Linux
en setting a breakpoint in kgdb. This was tested on an
Nvidia Jetson TK1 board with 4.2.0-rc5-next-20150805 kernel.
Regards,
Aapo Vienamo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More maj
For designs where EEPROMs are not connected to PCI Yukon2
chips we need to get the MAC address from the firmware.
Add a module parameter called 'mac_address' for this. It
will be used if no DT node can be found and the B2_MAC
register holds an invalid value.
Signed-off-by: Liviu Dudau
---
Add basic success/failure checking of the user string functions which
copy or find the length of userland strings.
The following cases are checked:
- strncpy_from_user() with legitimate user to kernel addresses, illegal
all-kernel and reversed addresses, and legitimate all-kernel
addresses.
-
Add basic success/failure checking of __clear_user() and clear_user(),
which zero an area of user or kernel memory and return the number of
bytes left to clear.
This catches a couple of bugs in the MIPS Enhanced Virtual Memory (EVA)
implementation (which have already been fixed):
test_user_copy:
Currently the test_user_copy module only tests the user accessors which
already check the address with access_ok(). Corresponding unchecked
accessors exist however which may be used after access_ok() is checked.
Since the addresses the test uses are known to be valid kernel
addresses, test these
Add basic success/failure checking of the combined user copy and
checksum functions which copy data between user and kernel space while
also checksumming that data. Some architectures have optimised versions
of these which combine both operations into a single pass.
The following cases are
Introduce managed counterparts for alloc_percpu() and free_percpu().
Add devm_alloc_percpu() and devm_free_percpu() into the managed
interfaces list.
Signed-off-by: Madalin Bucur
---
Documentation/driver-model/devres.txt | 4 +++
drivers/base/devres.c | 64
Allow the selection of the transmission queue based on the CPU id.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/Kconfig | 10 ++
drivers/net/ethernet/freescale/dpaa/dpaa_eth.c| 3 +++
drivers/net/ethernet/freescale/dpaa/dpaa_eth.h| 6
Hello,
On Tue, Aug 04, 2015 at 07:21:52PM -0700, Vikas Shivappa wrote:
> >I get that this would be an easier "bolt-on" solution but isn't a good
> >solution by itself in the long term. As I wrote multiple times
> >before, this is a really bad programmable interface. Unless you're
> >sure that
Add a series of counters to be exported through debugfs:
- add detailed counters for reception errors;
- add detailed counters for QMan enqueue reject events;
- count the number of fragmented skbs received from the stack;
- count all frames received on the Tx confirmation path;
- add congestion
Export per CPU counters through debugfs.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/Kconfig| 7 +
drivers/net/ethernet/freescale/dpaa/Makefile | 3 +
drivers/net/ethernet/freescale/dpaa/dpaa_debugfs.c | 272 +
> > + /* User explicitly set per-event callgraph, clear the old setting and
> reset. */
> > + if ((callgraph_buf != NULL) || (dump_size > 0)) {
> > +
> > + /* parse callgraph parameters */
> > + if (callgraph_buf != NULL) {
> > + if
Add support for basic ethtool operations.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/Makefile | 2 +-
.../net/ethernet/freescale/dpaa/dpaa_eth_common.c | 2 +
.../net/ethernet/freescale/dpaa/dpaa_eth_common.h | 3 +
Export Frame Queue and Buffer Pool IDs through sysfs.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/Makefile | 2 +-
drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 2 +
drivers/net/ethernet/freescale/dpaa/dpaa_eth.h | 3 +
Add trace points on the hot processing path.
Signed-off-by: Ruxandra Ioana Radulescu
---
drivers/net/ethernet/freescale/dpaa/Makefile | 1 +
drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 12 ++
drivers/net/ethernet/freescale/dpaa/dpaa_eth.h | 4 +
This introduces the Freescale Data Path Acceleration Architecture
(DPAA) Ethernet driver (dpaa_eth) that builds upon the DPAA QMan,
BMan, PAMU and FMan drivers to deliver Ethernet connectivity on
the Freescale DPAA QorIQ platforms.
Signed-off-by: Madalin Bucur
---
This patch series adds the Ethernet driver for the Freescale
QorIQ Data Path Acceleration Architecture (DPAA).
This version includes changes following the feedback received
on previous versions from Eric Dumazet, Bob Cochran, Joe Perches,
Paul Bolle, Joakim Tjernlund, Scott Wood, David Miller -
Add support for Scater/Gather (S/G) frames. The FMan can place
the frame content into multiple buffers and provide a S/G Table
(SGT) into one first buffer with references to the others.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 6 +
> ^
> cc1: all warnings being treated as errors
Sorry mistake in refactoring. I also forgot to include one patch.
I'll fix this and repost (and also add the man page)
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
CIR type serial ports aren't real serial ports.
This is just a way to prevent legacy 8250 serial
driver from probing and eventually binding some
resources.
Since in current state such ports aren't providing
any real functionality and it is not possible
to change their type via
On Fri, Jul 24, 2015 at 02:45:56PM +0300, Alexander Shishkin wrote:
> +#define __perf_err(__e, __c, __m) ({ \
> + static struct perf_err_site \
> + __attribute__ ((unused,__section__("__perf_err"))) \
> + __err_site = {
On Thu, Jul 30, 2015 at 11:16:36AM -0700, David Miller wrote:
> From: Michael Grzeschik
> Date: Thu, 30 Jul 2015 15:34:36 +0200
>
> > The commit <9c7077622dd9> ("packet: make packet_snd fail on len smaller
> > than l2 header") adds the check for minimum packet length of the used l2.
> > For
On Wed, Aug 05, 2015 at 07:42:24PM +0530, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Tuesday 04 August 2015 09:36 PM, Felipe Balbi wrote:
> > On Tue, Aug 04, 2015 at 08:50:41PM +0530, Kishon Vijay Abraham I wrote:
> >> No functional change. Previously omap_control_phy_power() was used to power
>
From: Joerg Roedel
This replaces the dmar_domain->iommu_bmp with a similar
reference count array. This allows us to keep track of how
many devices behind each iommu are attached to the domain.
This is necessary for further simplifications and
optimizations to the iommu<->domain attachment code.
From: Joerg Roedel
Simplify this function as much as possible with the new
iommu_refcnt field.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 50 +++--
1 file changed, 16 insertions(+), 34 deletions(-)
diff --git
From: Joerg Roedel
We don't need to do an expensive search for domain-ids
anymore, as we keep track of per-iommu domain-ids.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 15 +++
1 file changed, 3 insertions(+), 12 deletions(-)
diff --git
Hi Tony,
On 08/05/2015 05:28 AM, Tony Lindgren wrote:
> * Dave Gerlach [150717 13:59]:
>> --- a/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
>> +++ b/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
>> @@ -75,6 +75,14 @@ data that represent the following:
>> Cell #3
From: Joerg Roedel
Just call domain_remove_one_dev_info() for all devices in
the domain instead of reimplementing the functionality.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 20 ++--
1 file changed, 2 insertions(+), 18 deletions(-)
diff --git
From: Joerg Roedel
Rename this function and the ones further down its
call-chain to domain_context_clear_*. In particular this
means:
iommu_detach_dependent_devices -> domain_context_clear
iommu_detach_dev_cb -> domain_context_clear_one_cb
From: Joerg Roedel
Rename the function to dmar_remove_one_dev_info to match is
name better with its dmar_insert_one_dev_info counterpart.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git
From: Joerg Roedel
Move the code to attach/detach domains to iommus and vice
verce into a single function to make sure there are no
dangling references.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 124 +---
1 file changed, 49
On Wed, Aug 05, 2015 at 05:14:34PM +0200, Uladzislau Rezki wrote:
> While investigating “load balancer” logic, I run into interesting
> behavior related
> to affinity and NO_HZ idle balance. Basically saying if there are two
> tasks running
> in certain rq and one of them is pinned/affined, then
From: Joerg Roedel
Do the context-mapping of devices from a single place in the
call-path and clean up the other call-sites.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 33 -
1 file changed, 8 insertions(+), 25 deletions(-)
diff --git
From: Joerg Roedel
The code in the locked section does not touch anything
protected by the dmar_global_lock. Remove it from there.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c
From: Joerg Roedel
There is no need to make a difference here between VM and
non-VM domains, so simplify this code here.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c
Adjust set DAI format function in fsl_ssi driver
so it doesn't fail and clears RXDIR in AC'97 mode.
Signed-off-by: Maciej Szmigiero
---
Changes from v1: fix indentation to be consistent with rest
of the driver.
sound/soc/fsl/fsl_ssi.c |8 +---
1 files changed, 5 insertions(+), 3
Do not compute TMR in advance. Instead, set the TMR just before the interrupt
is accepted into the IRR. This limits the coupling between IOAPIC and LAPIC.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/ioapic.c | 9 ++---
arch/x86/kvm/ioapic.h | 3 +--
arch/x86/kvm/lapic.c | 19
From: Joerg Roedel
Rename this function to dmar_insert_one_dev_info() to match
the name better with its counter part function
domain_remove_one_dev_info().
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff
We can reuse the algorithm that computes the EOI exit bitmap to figure
out which vectors are handled by the IOAPIC. The only difference
between the two is for edge-triggered interrupts other than IRQ8
that have no notifiers active; however, the IOAPIC does not have to
do anything special for
Update MAINTAINERS file for HDLCD driver.
Cc: Andrew Morton
Cc: Arnd Bergmann
Cc: Mauro Carvalho Chehab
Cc: Greg KH
Cc: Joe Perches
Cc: Jiri Slaby
Signed-off-by: Liviu Dudau
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
This series adds support for ARM's HDLCD display controller found in Juno
and ARM TC2 Coretile. The HDLCD outputs an RGB stream that feeds into a
single digital encoder (DVI or HDMI).
This series depends on Sudeep Holla's series that introduces support for
SCPI[1] on Juno.
Only the Juno
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Signed-off-by: Liviu Dudau
---
.../devicetree/bindings/drm/arm/arm,hdlcd.txt | 74 ++
1 file changed, 74 insertions(+)
create mode 100644
The HDLCD controller is a display controller that supports resolutions
up to 4096x4096 pixels. It is present on various development boards
produced by ARM Ltd and emulated by the latest Fast Models from the
company.
Cc: David Airlie
Cc: Robin Murphy
Signed-off-by: Liviu Dudau
---
Instantiate AC'97 CODEC in fsl_ssi driver AC'97 mode.
Signed-off-by: Maciej Szmigiero
---
This is a resend without changes, to keep the whole series
together.
sound/soc/fsl/fsl_ssi.c | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git
The interrupt window is currently checked twice, once in vmx.c/svm.c and
once in dm_request_for_irq_injection. The only difference is the extra
check for kvm_arch_interrupt_allowed in dm_request_for_irq_injection,
and the different return value (EINTR/KVM_EXIT_INTR for vmx.c/svm.c vs.
ARM's Juno board has two HDLCD controllers, each linked to an NXP
TDA19988 HDMI transmitter that provides output encoding. Add them
to the device tree.
Signed-off-by: Liviu Dudau
---
arch/arm64/boot/dts/arm/juno-base.dtsi | 70 +-
1 file changed, 68
Avoid pointer chasing and memory barriers, and simplify the code
when split irqchip (LAPIC in kernel, IOAPIC/PIC in userspace)
is introduced.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/irq.c | 6 +++---
arch/x86/kvm/irq.h | 8
arch/x86/kvm/lapic.c | 4 ++--
arch/x86/kvm/mmu.c
I am going to push the memory barrier fixes to kvm/next.
The rest of the series is here for review. This includes cleanups from
myself and the bulk of the code from Steve.
Paolo
Paolo Bonzini (5):
KVM: x86: set TMR when the interrupt is accepted
KVM: x86: store IOAPIC-handled vectors in
On Wed, Aug 05, 2015 at 05:03:50PM +0200, Maciej S. Szmigiero wrote:
> On 05.08.2015 16:51, Greg Kroah-Hartman wrote:
> > On Wed, Aug 05, 2015 at 02:33:33PM +0200, Maciej S. Szmigiero wrote:
> >> CIR type serial ports aren't real serial ports.
> >>
> >> This is just a way to prevent legacy 8250
Check whether setting AC'97 ops succeeded and clean them
on removal so the fsl_ssi driver can be reloaded.
Signed-off-by: Maciej Szmigiero
---
This is a resend without changes, to keep the whole series
together.
sound/soc/fsl/fsl_ssi.c |9 -
1 files changed, 8 insertions(+), 1
On Tue, Aug 04, 2015 at 08:26:28PM -0700, Cong Wang wrote:
> (Cc'ing netdev for network issues)
>
> On Tue, Aug 4, 2015 at 6:42 AM, Shaun Crampton
> wrote:
> > Please CC me on any responses, thanks.
> >
> > Setting both ends of a veth to be oper UP completes very quickly but I
> > find that
From: Steve Rutherford
In order to support a userspace IOAPIC interacting with an in kernel
APIC, the EOI exit bitmaps need to be configurable.
If the IOAPIC is in userspace (i.e. the irqchip has been split), the
EOI exit bitmaps will be set whenever the GSI Routes are configured.
In
From: Steve Rutherford
Adds KVM_EXIT_IOAPIC_EOI which allows the kernel to EOI
level-triggered IOAPIC interrupts.
Uses a per VCPU exit bitmap to decide whether or not the IOAPIC needs
to be informed (which is identical to the EOI_EXIT_BITMAP field used
by modern x86 processors, but can also be
From: Steve Rutherford
In order to enable userspace PIC support, the userspace PIC needs to
be able to inject local interrupts even when the APICs are in the
kernel.
KVM_INTERRUPT now supports sending local interrupts to an APIC when
APICs are in the kernel.
The ready_for_interrupt_request
From: Joerg Roedel
This allows to do domain->iommu attachment after domain_init
has run.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
index
This will avoid an unnecessary trip to ->kvm and from there to the VPIC.
Signed-off-by: Paolo Bonzini
---
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/kvm/irq.c | 2 +-
arch/x86/kvm/lapic.c| 4 ++--
arch/x86/kvm/lapic.h| 4 ++--
arch/x86/kvm/svm.c
From: Steve Rutherford
First patch in a series which enables the relocation of the
PIC/IOAPIC to userspace.
Adds capability KVM_CAP_SPLIT_IRQCHIP;
KVM_CAP_SPLIT_IRQCHIP enables the construction of LAPICs without the
rest of the irqchip.
Compile tested for x86.
Signed-off-by: Steve Rutherford
AC'97 bus can support asymmetric playback/capture rates
so enable them in this case in fsl_ssi driver.
Signed-off-by: Maciej Szmigiero
---
This is a resend without changes, to keep the whole series
together.
sound/soc/fsl/fsl_ssi.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
From: Joerg Roedel
This struct contains all necessary information for the
function already. Also handle the info->dev == NULL case
while at it.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 33 +++--
1 file changed, 15 insertions(+), 18 deletions(-)
From: Joerg Roedel
There is no reason for this special handling of the
si_domain. The per-iommu domain-id can be allocated
on-demand like for any other domain. So remove the
pre-allocation code.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 28 +---
1
From: Joerg Roedel
When this lock is held the device_domain_lock is also
required to make sure the device_domain_info does not vanish
while in use. So this lock can be removed as it gives no
additional protection.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 87
From: Joerg Roedel
For devices without an PCI alias there will be two
device_domain_info structures added. Prevent that by
checking if the alias is different from the device.
Signed-off-by: Joerg Roedel
---
drivers/iommu/intel-iommu.c | 6 --
1 file changed, 4 insertions(+), 2
501 - 600 of 2158 matches
Mail list logo
