Before THP refcounting rework, THP was not allowed to cross VMA boundary.
So, if we have THP and we split it, PG_mlocked can be safely transfered to
small pages.
With new THP refcounting and naive approach to mlocking we can end up with
this scenario:
1. we have a mlocked THP, which belong to
With new refcounting we don't need to mark PMDs splitting. Let's drop
code to handle this.
pmdp_splitting_flush() is not needed too: on splitting PMD we will do
pmdp_clear_flush() + set_pte_at(). pmdp_clear_flush() will do IPI as
needed for fast_gup.
Signed-off-by: Kirill A. Shutemov
---
The patch updates Documentation/vm/transhuge.txt to reflect changes in
THP design.
Signed-off-by: Kirill A. Shutemov
Acked-by: Jerome Marchand
---
Documentation/vm/transhuge.txt | 151 ++---
1 file changed, 96 insertions(+), 55 deletions(-)
diff --git
Let's define page_mapped() to be true for compound pages if any
sub-pages of the compound page is mapped (with PMD or PTE).
On other hand page_mapcount() return mapcount for this particular small
page.
This will make cases like page_get_anon_vma() behave correctly once we
allow huge pages to be
We're going to use migration entries instead of compound_lock() to
stabilize page refcounts. Setup and remove migration entries require
page to be locked.
Some of split_huge_page() callers already have the page locked. Let's
require everybody to lock the page before calling split_huge_page().
Currently we don't split huge page on partial unmap. It's not an ideal
situation. It can lead to memory overhead.
Furtunately, we can detect partial unmap on page_remove_rmap(). But we
cannot call split_huge_page() from there due to locking context.
It's also counterproductive to do directly
With new refcounting we don't need to mark PMDs splitting. Let's drop
code to handle this.
pmdp_splitting_flush() is not needed too: on splitting PMD we will do
pmdp_clear_flush() + set_pte_at(). pmdp_clear_flush() will do IPI as
needed for fast_gup.
Signed-off-by: Kirill A. Shutemov
Tested-by:
We're going to have THP mapped with PTEs. It will confuse numabalancing.
Let's skip them for now.
Signed-off-by: Kirill A. Shutemov
Tested-by: Sasha Levin
Tested-by: Aneesh Kumar K.V
Acked-by: Jerome Marchand
---
mm/memory.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
With new THP refcounting, we don't need tricks to stabilize huge page.
If we've got reference to tail page, it can't split under us.
This patch effectively reverts a5b338f2b0b1.
Signed-off-by: Kirill A. Shutemov
Tested-by: Sasha Levin
Tested-by: Aneesh Kumar K.V
Acked-by: Jerome Marchand
---
On Fri, Sep 18, 2015 at 09:57:56PM +0900, Jungseok Lee wrote:
> On Sep 18, 2015, at 1:21 AM, Catalin Marinas wrote:
> > So, without any better suggestion for current_thread_info(), I'm giving
> > up the idea of using SPSel == 0 in the kernel. I'll look at your patch
> > in more detail. BTW, I
If you have physical access then the machine is yours to do with as you please.
Thinking of ATMs or voting machines that is a bold statement :-)
Thinking of mobile phones it depends on your jurisdiction.
Ortwin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
With new refcounting we don't need to mark PMDs splitting. Let's drop
code to handle this.
pmdp_splitting_flush() is not needed too: on splitting PMD we will do
pmdp_clear_flush() + set_pte_at(). pmdp_clear_flush() will do IPI as
needed for fast_gup.
Signed-off-by: Kirill A. Shutemov
---
With new refcounting we don't need to mark PMDs splitting. Let's drop
code to handle this.
Signed-off-by: Kirill A. Shutemov
---
arch/tile/include/asm/pgtable.h | 10 --
1 file changed, 10 deletions(-)
diff --git a/arch/tile/include/asm/pgtable.h b/arch/tile/include/asm/pgtable.h
index
We are going to use migration entries to stabilize page counts. It means
we don't need compound_lock() for that.
Signed-off-by: Kirill A. Shutemov
Tested-by: Sasha Levin
Tested-by: Aneesh Kumar K.V
Acked-by: Vlastimil Babka
Acked-by: Jerome Marchand
---
include/linux/mm.h | 35
With new refcounting we don't need to mark PMDs splitting. Let's drop
code to handle this.
Signed-off-by: Kirill A. Shutemov
Tested-by: Sasha Levin
Acked-by: Jerome Marchand
---
arch/x86/include/asm/pgtable.h | 9 -
arch/x86/include/asm/pgtable_types.h | 2 --
On 09/18, Peter Zijlstra wrote:
>
> On Fri, Sep 18, 2015 at 03:28:44PM +0200, Oleg Nesterov wrote:
> > On 09/18, Peter Zijlstra wrote:
> > >
> > > ns = pid->numbers[pid->level].ns;
> > > if ((atomic_read(>count) == 1) ||
> > >atomic_dec_and_test(>count)) {
> > >
> > > +
As with rmap, with new refcounting we cannot rely on PageTransHuge() to
check if we need to charge size of huge page form the cgroup. We need to
get information from caller to know whether it was mapped with PMD or
PTE.
We do uncharge when last reference on the page gone. At that point if we
see
Hi Russell,
On Fri, 2015-09-18 at 10:56AM +0100, Russell King - ARM Linux wrote:
> Sorry guys, some of you will get the patches twice, as Sören's name
> in the header caused vger to reject all the patches.
That is the first time I hear about an issue like that. I've been
receiving patches fine
omap-gpmc.c is a memory controller so move the binding to the
right place.
Signed-off-by: Roger Quadros
---
.../bindings/{bus/ti-gpmc.txt => memory-controllers/omap-gpmc.txt}| 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename Documentation/devicetree/bindings/{bus/ti-gpmc.txt
I personally think this is opening a can of worms. Now it's just a list
of alternative root devices. But the kernel knows absolutely nothing
about these. When is it fine to try an alternative? Why did the first
one not work? Did we just not wait long enough? Or is it a failed RAID
device? Or is
We are going to use migration PTE entries to stabilize page counts.
If the page is mapped with PMDs we need to split the PMD and setup
migration entries. It's reasonable to combine these operations to avoid
double-scanning over the page table.
Signed-off-by: Kirill A. Shutemov
Tested-by: Sasha
We're going to allow mapping of individual 4k pages of THP compound
page. It means we cannot rely on PageTransHuge() check to decide if
map/unmap small page or THP.
The patch adds new argument to rmap functions to indicate whether we want
to operate on whole compound page or only the small page.
This patch adds implementation of split_huge_page() for new
refcountings.
Unlike previous implementation, new split_huge_page() can fail if
somebody holds GUP pin on the page. It also means that pin on page
would prevent it from bening split under you. It makes situation in
many places much
The GPMC WAIT pin status are now available over gpiolib.
Update the omap_dev_ready() function to use gpio instead of
directly accessing GPMC register space.
Signed-off-by: Roger Quadros
---
drivers/mtd/nand/omap2.c | 29 +---
The WAIT pins support either rising or falling edge interrupts
so add irqchip support to the gpiochip model.
Signed-off-by: Roger Quadros
---
drivers/memory/omap-gpmc.c | 132 +
1 file changed, 132 insertions(+)
diff --git
Em Fri, Sep 18, 2015 at 02:37:09PM +0100, Mark Rutland escreveu:
> > > So it looks like I shouldn't have any synthesized events. Have I missed
> > > anything?
> >
> > Yes, you are right. But you are not getting the COMM and MMAP events from
> > the exec which means you are killing perf before it
On Fri, Sep 18, 2015 at 04:58:28PM +0200, Nicolas Ferre wrote:
> From: Sylvain Rochet
>
> The recently added endpoint capabilities flags verification breaks Atmel
> USBA because the endpoint configuration was only added when the driver
> is bound using the legacy pdata interface.
>
> Convert
Add compatible id, GPMC register resource and interrupt
resource to NAND controller nodes.
The GPMC driver now implements gpiochip and irqchip so
enable gpio-controller and interrupt-controller properties.
With this the interrupt parent of NAND node changes so fix it
accordingly.
Signed-off-by:
On these boards NAND ready pin status is avilable over
GPMC_WAIT0 pin.
For NAND we don't use GPMC wait pin monitoring but
get the NAND Ready/Busy# status using GPIOlib.
GPMC driver provides the WAIT0 pin status over GPIOlib.
Read speed increases from 16516 KiB/ to 18813 KiB/s
and write speed was
On 17.09.2015 20:28, Drew DeVault wrote:
I don't think this is a strong argument against this feature. The
implementation of this feature
will be pretty straightfoward - only a small part of the code has to actually
change its behavior
and it can do without changing the interfaces it already
From: Sylvain Rochet
The recently added endpoint capabilities flags verification breaks Atmel
USBA because the endpoint configuration was only added when the driver
is bound using the legacy pdata interface.
Convert endpoint configuration to new capabilities model when driver is
bound to a
On 18/09/2015 16:29, Feng Wu wrote:
> VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
> With VT-d Posted-Interrupts enabled, external interrupts from
> direct-assigned devices can be delivered to guests without VMM
> intervention when guest is running in non-root mode.
>
On these boards NAND ready pin status is avilable over
GPMC_WAIT0 pin.
Read speed increases from 13768 KiB/ to 17246 KiB/s.
Write speed was unchanged at 7123 KiB/s.
Measured using mtd_speedtest.ko.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/dra7-evm.dts | 1 +
Add compatible id, GPMC register resource and interrupt
resource to NAND controller nodes.
The GPMC driver now implements gpiochip and irqchip so
enable gpio-controller and interrupt-controller properties.
With this the interrupt parent of NAND node changes so fix it
accordingly.
Signed-off-by:
Add compatible id, GPMC register resource and interrupt
resource to NAND controller nodes.
The GPMC driver now implements gpiochip and irqchip so
enable gpio-controller and interrupt-controller properties.
With this the interrupt parent of NAND node changes so fix it
accordingly.
Signed-off-by:
Make gpmc node gpio+interrupt capable.
Add compatible id, interrupt and wait pin to NAND node.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/dm8168-evm.dts | 7 ---
arch/arm/boot/dts/dm816x.dtsi| 4
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git
On 17 September 2015 at 17:52, Alan Stern wrote:
> On Thu, 17 Sep 2015, Tomeu Vizoso wrote:
>
>> Some buses (eg. AMBA) need access to some HW resources (it may need a
>> clock to be enabled so a device ID can be read) before a device can be
>> matched to a driver.
>>
>> The pre_probe callback
GPMC_STATUS register is private to the GPMC module and must not be
accessed directly by NAND driver through the gpmc_regs.
They must use gpmc_omap_get_nand_ops() instead.
Signed-off-by: Roger Quadros
---
drivers/memory/omap-gpmc.c | 2 +-
We have been preventing mapping GPMC children in the
first 1MB but really it has to be the first 16MB as
the minimum GPMC partition size is 16MB.
Also print an error message if CS mapping fails
due to DT requesting address outside the GPMC
map.
Signed-off-by: Roger Quadros
---
Add compatible id, GPMC register resource and interrupt
resource to NAND controller nodes.
The GPMC driver now implements gpiochip and irqchip so
enable gpio-controller and interrupt-controller properties.
With this the interrupt parent of NAND node changes so fix it
accordingly.
Signed-off-by:
On these boards NAND ready pin status is avilable over
GPMC_WAIT0 pin.
For NAND we don't use GPMC wait pin monitoring but
get the NAND Ready/Busy# status using GPIOlib.
GPMC driver provides the WAIT0 pin status over GPIOlib.
Read speed increases from 7869 KiB/ to 8875 KiB/s
and write speed was
OMAPs can have 2 to 4 WAITPINs that can be used as general purpose
input if not used for memory wait state insertion.
The first user will be the OMAP NAND chip to get the NAND
read/busy status using gpiolib.
Signed-off-by: Roger Quadros
---
drivers/memory/omap-gpmc.c | 130
Move NAND specific device tree parsing to NAND driver.
The NAND controller node must have a compatible id, register space
resource and interrupt resource.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/gpmc-nand.c | 5 +-
drivers/memory/omap-gpmc.c | 135
Copy all the platform data parameters to the driver's local data
structure 'omap_nand_info' and use it in the entire driver. This will
make it easer for device tree migration.
Signed-off-by: Roger Quadros
---
drivers/mtd/nand/omap2.c | 26 ++
1 file changed, 18
This is needed by OMAP NAND driver to poll the empty status
of the writebuffer.
Signed-off-by: Roger Quadros
---
drivers/memory/omap-gpmc.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index
Hi,
We do a couple of things in this series which result in
cleaner device tree implementation, faster perfomance and
multi-platform support. As an added bonus we get new GPI/Interrupt pins
for use in the system.
- Establish a custom interface between NAND and GPMC driver. This is
needed because
No code changes.
Signed-off-by: Denys Vlasenko
CC: Ingo Molnar
CC: Borislav Petkov
CC: "H. Peter Anvin"
CC: Andy Lutomirski
CC: Kees Cook
CC: x...@kernel.org
CC: linux-kernel@vger.kernel.org
---
arch/x86/math-emu/fpu_entry.c | 43 +--
1 file changed,
Run-tested by booting with "no387 nofxsr" and running test program:
# ./test_FCOMI
[RUN] Testing f[u]comi[p] instructions
[OK]f[u]comi[p]
Signed-off-by: Denys Vlasenko
CC: Ingo Molnar
CC: Borislav Petkov
CC: "H. Peter Anvin"
CC: Andy Lutomirski
CC: Kees Cook
CC: x...@kernel.org
CC:
On 18 September 2015 at 15:07, Herbert Xu wrote:
> On Thu, Sep 17, 2015 at 02:45:50PM +0100, Lee Jones wrote:
>> v1 => v2:
>> - New patch: Also fixing /dev/hw_random => /dev/hwrng in Kconfig
>> - Fix 2099 => 2009 typo in commit log
>> - Fix 'number of random numbers sourced' return value
>> -
On 09/18/2015 09:33 AM, Ingo Molnar wrote:
>
> * Denys Vlasenko wrote:
>
>> Run-tested by booting with "no387 nofxsr" and running test programs:
>>
>> # ./test_FCMOV
>> [RUN]Testing fcmovCC instructions
>> [OK] fcmovCC
>> # ./test_FCOMI
>> [RUN]Testing f[u]comi[p] instructions
Run-tested by booting with "no387 nofxsr" and running test program:
# ./test_FCMOV
[RUN] Testing fcmovCC instructions
[OK]fcmovCC
Signed-off-by: Denys Vlasenko
CC: Ingo Molnar
CC: Borislav Petkov
CC: "H. Peter Anvin"
CC: Andy Lutomirski
CC: Kees Cook
CC: x...@kernel.org
CC:
On Fri, Sep 18, 2015 at 05:25:07PM +0300, Kirill A. Shutemov wrote:
> On Thu, Sep 17, 2015 at 09:29:27AM -0700, Guenter Roeck wrote:
> > Hi,
> >
> > my crisv32 qemu test fails with next-20150917 as follows.
> >
> > NET: Registered protocol family 16
> > kernel BUG at mm/slab.c:1648!
> > Linux
Select IRQ_BYPASS_MANAGER for x86 when CONFIG_KVM is set
Signed-off-by: Feng Wu
---
arch/x86/kvm/Kconfig | 2 ++
arch/x86/kvm/Makefile | 3 +++
2 files changed, 5 insertions(+)
diff --git a/arch/x86/kvm/Kconfig b/arch/x86/kvm/Kconfig
index d8a1d56..c951d44 100644
--- a/arch/x86/kvm/Kconfig
From: Eric Auger
Move _irqfd_resampler and _irqfd struct declarations in a new
public header: kvm_irqfd.h. They are respectively renamed into
kvm_kernel_irqfd_resampler and kvm_kernel_irqfd. Those datatypes
will be used by architecture specific code, in the context of
IRQ bypass manager
On 18/09/2015 16:46, Nicholas Krause wrote:
> This fixes the incorrect assumation that the function
> kvm_vcpu_write_guest always runs successfully and
> therefore checks if it fails by returning a error code
> and if so return immediately to the caller of the function
> process_smi as we cannot
On 09/17/2015 11:09 PM, Greg Thelen wrote:
> I'm not denying the issue, bug the WARNING splat isn't necessarily
> catching a problem. The corresponding code comes from your debug patch:
> +
> WARN_ONCE(__this_cpu_read(memcg->stat->count[MEM_CGROUP_STAT_DIRTY]) >
> (1UL<<30),
From: Eric Auger
This patch introduces
- kvm_arch_irq_bypass_add_producer
- kvm_arch_irq_bypass_del_producer
- kvm_arch_irq_bypass_stop
- kvm_arch_irq_bypass_start
They make possible to specialize the KVM IRQ bypass consumer in
case CONFIG_KVM_HAVE_IRQ_BYPASS is set.
Signed-off-by: Eric Auger
SysFS rules stipulate that only one value can be conveyed per
file. As such splitting the "status" interface in individual files.
This is also be useful for user space application - that way they can
probe each file individually rather than having to parse a list of entries.
Signed-off-by:
On 18/09/2015 15:39, Igor Mammedov wrote:
> When INIT/SIPI sequence is sent to VCPU which before that
> was in use by OS, VMRUN might fail with:
>
> KVM: entry failed, hardware error 0x
> EAX= EBX= ECX= EDX=06d3
> ESI= EDI= EBP=
Le 08/08/2015 12:11, Alexandre Belloni a écrit :
> Instead of having to add a new configuration option each time support for
> new SoC is added, use CONFIG_DEBUG_UART_PHYS. For now,
> CONFIG_DEBUG_UART_VIRT is automatically computed.
>
> Signed-off-by: Alexandre Belloni
> ---
>
On 09/18, Dmitry Vyukov wrote:
>
> On Fri, Sep 18, 2015 at 3:44 PM, Oleg Nesterov wrote:
> > So I assume that if we have
> >
> > int X = 0;
> > atomic_t Y = ATOMIC_INIT(0);
> >
> > void w(void)
> > {
> > X = 1;
> >
Extend struct pi_desc for VT-d Posted-Interrupts.
Signed-off-by: Feng Wu
---
arch/x86/kvm/vmx.c | 20 ++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 83b7b5c..271dd70 100644
--- a/arch/x86/kvm/vmx.c
+++
This patch defines a new interface kvm_intr_is_single_vcpu(),
which can returns whether the interrupt is for single-CPU or not.
It is used by VT-d PI, since now we only support single-CPU
interrupts, For lowest-priority interrupts, if user configures
it via /proc/irq or uses irqbalance to make it
Without access to the device tree, it is impossible to know
what CPU a tracer is affined to. As such adding a new sysFS
interface to convey the information.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm3x.c | 13 +
1 file changed, 13 insertions(+)
Implement the following callbacks for x86:
- kvm_arch_irq_bypass_add_producer
- kvm_arch_irq_bypass_del_producer
- kvm_arch_irq_bypass_stop: dummy callback
- kvm_arch_irq_bypass_resume: dummy callback
and set CONFIG_HAVE_KVM_IRQ_BYPASS for x86.
Signed-off-by: Feng Wu
---
v8:
- Move the weak
This patch adds the routine to update IRTE for posted-interrupts
when guest changes the interrupt configuration.
Signed-off-by: Feng Wu
---
v9:
- Check !kvm_arch_has_assigned_device(kvm) first then
!irq_remapping_cap(IRQ_POSTING_CAP)
v8:
- Move 'kvm_arch_update_pi_irte' to vmx.c as a callback
On Fri, 18 Sep 2015, Kohji Okuno wrote:
>
> irq thread(runs sdhci_thread_irq()) is waiting on
> drivers/mmc/core/core.c:mmc_wait_for_req_done() in order to access
> a SDIO register. And, this thread shoud be woken up from
> sdhci_irq() after the completion of the register access.
> But, since the
This patch adds the registration/unregistration of an
irq_bypass_producer for MSI/MSIx on vfio pci devices.
Signed-off-by: Feng Wu
---
v8:
- Merge "[PATCH v7 08/17] vfio: Select IRQ_BYPASS_MANAGER for vfio PCI devices"
into this patch.
v6:
- Make the add_consumer and del_consumer callbacks
This patch adds an arch specific hooks 'arch_update' in
'struct kvm_kernel_irqfd'. On Intel side, it is used to
update the IRTE when VT-d posted-interrupts is used.
Signed-off-by: Feng Wu
---
v9:
- Use 'if' instead of "? :" in kvm_arch_update_irqfd_routing()
- coding style
v8:
- Remove callback
This patch updates the Posted-Interrupts Descriptor when vCPU
is preempted.
sched out:
- Set 'SN' to suppress furture non-urgent interrupts posted for
the vCPU.
sched in:
- Clear 'SN'
- Change NDST if vCPU is scheduled to a different CPU
- Set 'NV' to POSTED_INTR_VECTOR
Signed-off-by: Feng Wu
The comment before the `COMEDI_SRF_...` macros starts with a kernel-doc
mark but isn't valid kernel-doc. There isn't a kernel-doc template for
a group of macro constants. These macros are all private anyway, so
don't really need to be in kernel-doc. Just change it to a normal
comment.
On Fri, 18 Sep 2015, Sudip Mukherjee wrote:
> On Wed, Sep 16, 2015 at 12:54:03PM -0400, Alan Stern wrote:
> > On Wed, 16 Sep 2015, Sudip Mukherjee wrote:
> >
> > > On error find_tt() returns either a NULL pointer or the error value in
> > > ERR_PTR. But we were dereferencing it directly without
This patch updates the Posted-Interrupts Descriptor when vCPU
is blocked.
pre-block:
- Add the vCPU to the blocked per-CPU list
- Set 'NV' to POSTED_INTR_WAKEUP_VECTOR
post-block:
- Remove the vCPU from the per-CPU list
Signed-off-by: Feng Wu
---
v9:
- Add description for
Enable VT-d Posted-Interrtups and add a command line
parameter for it.
Signed-off-by: Feng Wu
Reviewed-by: Paolo Bonzini
---
Documentation/kernel-parameters.txt | 1 +
drivers/iommu/irq_remapping.c | 12
2 files changed, 9 insertions(+), 4 deletions(-)
diff --git
Make kvm_set_msi_irq() public, we can use this function outside.
Signed-off-by: Feng Wu
Reviewed-by: Paolo Bonzini
---
v8:
- Export kvm_set_msi_irq() so we can use it in vmx code
arch/x86/include/asm/kvm_host.h | 4
arch/x86/kvm/irq_comm.c | 5 +++--
2 files changed, 7
From: Eric Auger
This patch adds the registration/unregistration of an
irq_bypass_consumer on irqfd assignment/deassignment.
Signed-off-by: Eric Auger
Signed-off-by: Feng Wu
---
v4 -> v5:
- due to removal of static inline stubs, add
#ifdef CONFIG_HAVE_KVM_IRQ_BYPASS
around consumer
From: Alex Williamson
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 before being injected into the VM.
However, hardware technologies exist that often allow the host to be
Move struct kvm_irq_routing_table from irqchip.c to kvm_host.h,
so we can use it outside of irqchip.c.
Signed-off-by: Feng Wu
Reviewed-by: Paolo Bonzini
---
include/linux/kvm_host.h | 14 ++
virt/kvm/irqchip.c | 10 --
2 files changed, 14 insertions(+), 10
From: Eric Auger
Select IRQ_BYPASS_MANAGER when CONFIG_KVM is set
Also add compilation of virt/lib.
Signed-off-by: Eric Auger
Signed-off-by: Feng Wu
---
v3 -> v4:
- add compilation of virt/lib in arm/arm64 KVM
v2 -> v3:
- [Feng Wu] Correct a typo in 'arch/arm64/kvm/Kconfig'
v1 -> v2:
- also
This patch adds some helper functions to manipulate the
Posted-Interrupts Descriptor.
Signed-off-by: Feng Wu
Reviewed-by: Paolo Bonzini
---
arch/x86/kvm/vmx.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index
VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
With VT-d Posted-Interrupts enabled, external interrupts from
direct-assigned devices can be delivered to guests without VMM
intervention when guest is running in non-root mode.
You can find the VT-d Posted-Interrtups Spec. in
Possibly 'multirootdelay'?
I had the same thought, but wanted to avoid using any prefix other than
root*= since it would break tradition for this part of the kernel.
However, is there any case you can think of for wanting the values to be
different between rootdelay and the per-device scan
On 18/09/15 15:34, Punit Vara wrote:
This patch is to the comedilib.h file that fixes up coding style issues
and following warning:
- Block comments use * on subsequent lines
Signed-off-by: Punit Vara
---
drivers/staging/comedi/comedilib.h | 28 ++--
1 file changed,
Hi Linus,
Please pull the following fixes for 4.3-rc2. This update contains 7
fixes for problems ranging from build failures to incorrect error
reporting.
thanks,
-- Shuah
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
Le 10/08/2015 16:46, Alexandre Belloni a écrit :
> struct at91_udc_data is now only used inside the driver, move it to its
> include.
>
> Signed-off-by: Alexandre Belloni
Acked-by: Nicolas Ferre
Thanks.
> ---
> drivers/usb/gadget/udc/at91_udc.h | 8
>
On 09/17/2015 05:34 PM, Ebru Akagunduz wrote:
> max_ptes_swap specifies how many pages can be brought in from
> swap when collapsing a group of pages into a transparent huge page.
>
> /sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_swap
>
> A higher value can cause excessive swap IO and
On 2015-09-17 14:40, Richard Weinberger wrote:
Am 17.09.2015 um 20:37 schrieb Austin S Hemmelgarn:
On 2015-09-17 13:47, Richard Weinberger wrote:
On Thu, Sep 17, 2015 at 1:49 PM, Drew DeVault wrote:
On 2015-09-17 1:40 PM, Ortwin Glück wrote:
You can do that completely in user space from an
Le 10/08/2015 16:41, Alexandre Belloni a écrit :
> include/linux/platform_data/atmel.h has a lot of useless includes, remove
> them.
>
> Signed-off-by: Alexandre Belloni
Acked-by: Nicolas Ferre
And I take it in at91-4.4-soc branch.
Thanks, bye.
> ---
> include/linux/platform_data/atmel.h
> -Original Message-
> From: Shawn Guo [mailto:shawn...@kernel.org]
> Sent: 2015年9月18日 9:15
> To: Wang Shenwei-B38339
> Cc: ja...@lakedaemon.net; Huang Yongcai-B20788;
> linux-kernel@vger.kernel.org; ker...@pengutronix.de; Sudeep Holla;
> t...@linutronix.de; shawn@linaro.org;
Le 10/08/2015 16:29, Alexandre Belloni a écrit :
> Definitions from linux/platform_data/atmel.h are not used, remove the
> include.
>
> Signed-off-by: Alexandre Belloni
Acked-by: Nicolas Ferre
> ---
> drivers/usb/gadget/udc/atmel_usba_udc.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff
I git clone and git pull the latest linux kernel.
When I make pdfdocs, it reports the following error to me.
But I checked the filesystems.xml:14946, no error found.
---
PDF
This patch is to the comedilib.h file that fixes up coding style issues
and following warning:
- Block comments use * on subsequent lines
Signed-off-by: Punit Vara
---
drivers/staging/comedi/comedilib.h | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff
Le 10/09/2015 10:19, Alexandre Belloni a écrit :
> When CONFIG_PM is defined but not CONFIG_PM_SLEEP (this happens when
> CONFIG_SUSPEND is not defined), there is the following warning:
>
> drivers/spi/spi-atmel.c:1723:12: warning: ‘atmel_spi_suspend’ defined but not
> used [-Wunused-function]
>
On 09/18/2015 07:57 AM, LABBE Corentin wrote:
Some driver use a modified version of sg_nents_for_len with an
additional parameter bool *chained for knowing if the scatterlist is
chained or not.
So, for removing duplicate code, add sg_nents_len_chained in
lib/scatterlist.c
Signed-off-by: LABBE
On 2015-09-17 13:30, Drew DeVault wrote:
That said, using the term failover for this is probably not the best
idea, many people associate it almost exclusively with online failover
and high-availability setups, and trying to do something like that with
the root file system is just asking for
Le 02/09/2015 18:24, Alexandre Belloni a écrit :
> Atmel SAMA5 SoCs are also supported through mach-at91.
>
> Signed-off-by: Alexandre Belloni
Absolutely:
Acked-by: Nicolas Ferre
Thanks.
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
Em Fri, Sep 18, 2015 at 11:28:30AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Sep 18, 2015 at 11:26:22AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Fri, Sep 18, 2015 at 01:39:13AM +, 平松雅巳 / HIRAMATU，MASAMI escreveu:
> > > Could you pull this bugfix as an urgent patch, since this
On Fri, Sep 18, 2015 at 03:14:26PM +0100, Mark Salter wrote:
> Currently, DMI initialization takes place in a core initcall. This
> limits how early in boot the kernel can make DMI-based decisions
> about firmware/hardware quirks. This patch moves DMI initialization
> to setup_arch() so that DMI
On 09/18/2015 12:06 AM, Linus Torvalds wrote:
Gaah, my mailer autocompleted Jens' email with an old one..
Sorry for the repeat email with the correct address.
On Thu, Sep 17, 2015 at 11:04 PM, Linus Torvalds
wrote:
On Thu, Sep 17, 2015 at 10:40 PM, Dave Chinner wrote:
PS: just hit another
Hi Steve,
On 18/09/15 14:45, Steven Rostedt wrote:
> On Fri, 18 Sep 2015 11:55:47 +0100
> Kapileshwar Singh wrote:
>
> Perhaps we need to make addr into a unsigned long long, and then add:
>
> addr = (pevent->long_size == 8) ?
> *(unsigned long long *)(data +
401 - 500 of 1682 matches
Mail list logo
