Cc: Al Viro
Signed-off-by: Rasmus Villemoes
---
lib/test_printf.c | 27 +++
1 file changed, 27 insertions(+)
diff --git a/lib/test_printf.c b/lib/test_printf.c
index 60740c10c3e8..0234356c6698 100644
--- a/lib/test_printf.c
+++ b/lib/test_printf.c
@@ -13,6 +13,7 @@
These should also count as performed tests.
Acked-by: Kees Cook
Signed-off-by: Rasmus Villemoes
---
lib/test_printf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/test_printf.c b/lib/test_printf.c
index b23ce824766f..3e21170d327d 100644
--- a/lib/test_printf.c
+++
The kernel's printf doesn't follow the standards in a few corner cases
(which are probably mostly irrelevant). Add tests that document the
current behaviour.
Cc: Kees Cook
Signed-off-by: Rasmus Villemoes
---
lib/test_printf.c | 21 +++--
1 file changed, 15 insertions(+), 6
Following "lib/vsprintf.c: expand field_width to 24 bits", let's add a
test to see that we now actually support bitmaps with 65536 bits.
Cc: Maurizio Lombardi
Cc: Tejun Heo
Acked-by: Kees Cook
Signed-off-by: Rasmus Villemoes
---
lib/test_printf.c | 17 +
1 file changed, 17
kasprintf relies on being able to replay the formatting and getting
the same result (in particular, the same length). This will almost
always work, but it is possible that the object pointed to by a %s or
%p argument changed under us (so we might get truncated output). Add a
somewhat paranoid
On Thu 2015-10-15 13:25:59, Florian Fainelli wrote:
> On 15/10/15 12:59, Dinh Nguyen wrote:
> > On 10/15/2015 03:03 PM, Florian Fainelli wrote:
> >> On 15/10/15 12:09, Dinh Nguyen wrote:
> >>> Hi,
> >>>
> >>> commit "8b63ec1837fa phylib: Make PHYs children of their MDIO bus, not
> >>> the bus'
We need to make sure that the offset is valid before manipulating it,
otherwise it might overflow on the multiplication.
Signed-off-by: Sasha Levin
---
kernel/time/ntp.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/time/ntp.c b/kernel/time/ntp.c
index
On Thu, Dec 03, 2015 at 11:33:24AM +0100, Nicolas Ferre wrote:
> Le 03/12/2015 10:53, Ludovic Desroches a écrit :
> > A new compatible string has been introduced: atmel,sama5d4-i2c. It
> > allows to use the i2c-sda-hold-time-ns property if needed.
> >
> > Signed-off-by: Ludovic Desroches
>
>
On Thursday 03 December 2015 21:14:41 Yury Norov wrote:
>
> > I'm not sure there is much value in
> > keeping 4*PAGE_SIZE for larger page sizes but I agree that the current
> > 16K value doesn't work well with 64K pages.
>
> Arnd told there will be a workaround for arm v6 caches. Than this
>
On Thu, Dec 03, 2015 at 02:26:16PM -0500, Tejun Heo wrote:
> + WARN_ONCE(current->flags & PF_MEMALLOC,
I'm not sure about using PF_MEMALLOC for detecting reclaim. There appear
to be more sites setting this than reclaim. See:
drivers/block/nbd.c:current->flags |= PF_MEMALLOC;
On Thu, Dec 03, 2015 at 03:35:21PM +0200, Stanimir Varbanov wrote:
> From: Stanimir Varbanov
>
> Document Qualcomm PCIe driver devicetree bindings.
>
> Signed-off-by: Stanimir Varbanov
> Signed-off-by: Stanimir Varbanov
Acked-by: Rob Herring
> ---
>
On Thu, Dec 03, 2015 at 12:33:57PM -0800, Brian Norris wrote:
> On Thu, Dec 03, 2015 at 12:19:08PM -0800, Dmitry Torokhov wrote:
> > On Thu, Dec 03, 2015 at 04:48:40PM +0800, Caesar Wang wrote:
> > > As the Dan report the smatch check the thermal driver warning:
> > >
Hi Yang.
On Wed, Nov 25, 2015 at 02:45:43PM -0800, Yang Shi wrote:
> Check if user address is accessible in atomic version __get_user_pages_fast()
> before walking the page table.
> And, check if end > start in get_user_pages_fast(), otherwise fallback to slow
> path.
Two different but related
On 3 December 2015 at 03:32, Alexander Shishkin
wrote:
> In order to ensure safe aux buffer management, we rely on the assumption
> that pmu::stop() stops its ongoing aux transaction and not just the hw.
>
> This patch documents this requirement for perf_aux_output_{begin,end}()
> apis.
>
>
On Wed, Dec 02, 2015 at 02:58:21PM -0800, James Bottomley wrote:
> On Tue, 2015-12-01 at 21:20 +0100, Andrea Gelmini wrote:
> OK, this looks like some type of problem with a USB enclosure. It's
> probably misreporting something in the mode pages. can you run sg_ses
> on whatever /dev/sg the
On Thu, Dec 03, 2015 at 12:19:08PM -0800, Dmitry Torokhov wrote:
> On Thu, Dec 03, 2015 at 04:48:40PM +0800, Caesar Wang wrote:
> > As the Dan report the smatch check the thermal driver warning:
> > drivers/thermal/rockchip_thermal.c:551 rockchip_configure_from_dt()
> > warn: impossible condition
On Thu, Dec 03, 2015 at 11:41:39AM -0800, Davidlohr Bueso wrote:
> >+#define smp_cond_acquire(cond) do {\
> >+while (!(cond)) \
> >+cpu_relax();\
> >+smp_rmb(); /* ctrl + rmb := acquire */ \
> >+} while (0)
>
> So
[1.] One line summary of the problem:
Erratic fan speed and little control kernel 4.2
[2.] Full description of the problem/report:
After upgrading to kernel 4.2 my CPU fan started speeding and slowing
without good reason even when the PC is idle.
sensors shows:
it8721-isa-0a10
Adapter: ISA
From: Stephen Boyd
Date: Wed, 2 Dec 2015 23:55:15 -0800
> Typically we return error pointers when we want to use those
> pointers in the non-error case, but this function is just
> returning error pointers or NULL for success. Change the style to
> plain int to follow normal kernel coding
On Thu, Dec 03, 2015 at 04:37:26PM +, Will Deacon wrote:
> > +#define smp_cond_acquire(cond) do {\
> > + while (!(cond)) \
> > + cpu_relax();\
> > + smp_rmb(); /* ctrl + rmb := acquire */ \
> > +} while (0)
> > +
Reading or Writing of PCI VPD data causes system panic.
We saw this problem by running "lspci -vvv" in the beginning.
However this can be easily reproduced by running
cat /sys/bus/devices/XX../vpd
VPD length has been set as 32768 by default. Accessing vpd
will trigger read/write of 32k. This
From:
Date: Thu, 3 Dec 2015 09:19:14 +0200
> +static u32 crc_table[256] = {
No way.
We have every conceivable implementation of CRC calculations in the
kernel already. Use them.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, Dec 03, 2015 at 04:48:40PM +0800, Caesar Wang wrote:
> As the Dan report the smatch check the thermal driver warning:
> drivers/thermal/rockchip_thermal.c:551 rockchip_configure_from_dt()
> warn: impossible condition '(thermal->tshut_temp > ((~0 >> 1))) =>
> (s32min-s32max > s32max)'
>
>
From: Stas Sergeev
Date: Wed, 2 Dec 2015 20:32:24 +0300
> These 2 patches add an ability to control the
> autonegotiation via ethtool. For example:
>
> ethtool -s eth0 autoneg off
> ethtool -s eth0 autoneg on
>
> This is needed if you want to connect the mvneta's MII
> to different switches or
> /* INST_RETIRED.ANY_P, inv=1, cmask=16 (cycles:p). */
> INTEL_FLAGS_EVENT_CONSTRAINT(0x108000c0, 0x01),
> + /* Allow all events as PEBS with no flags */
> + INTEL_ALL_EVENT_CONSTRAINT(0, 0x1),
I don't think this is really needed (no extra PEBS events), but ok it shouldn't
From: Thierry Reding
Date: Wed, 2 Dec 2015 17:30:26 +0100
> From: Thierry Reding
>
> These new helpers simplify implementing multi-driver modules and
> properly handle failure to register one driver by unregistering all
> previously registered drivers.
>
> Signed-off-by: Thierry Reding
From: Thierry Reding
Date: Wed, 2 Dec 2015 17:30:27 +0100
> From: Thierry Reding
>
> These new helpers simplify implementing multi-driver modules and
> properly handle failure to register one driver by unregistering all
> previously registered drivers.
>
> Signed-off-by: Thierry Reding
From: Thierry Reding
Date: Wed, 2 Dec 2015 17:30:28 +0100
> From: Thierry Reding
>
> These new helpers simplify implementing multi-driver modules and
> properly handle failure to register one driver by unregistering all
> previously registered drivers.
>
> Signed-off-by: Thierry Reding
From: Thierry Reding
Date: Wed, 2 Dec 2015 17:30:29 +0100
> From: Thierry Reding
>
> These new helpers simplify implementing multi-driver modules and
> properly handle failure to register one driver by unregistering all
> previously registered drivers.
>
> Signed-off-by: Thierry Reding
Patches not properly CC:'d to netdev will not be queued up in patchwork, and
therefore will also be ignored.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Tejun,
I share Don's concern about connecting the soft lockup detector and the
workqueue watchdog to the same kernel parameter in /proc. I would feel
more comfortable if the workqueue watchdog had its dedicated parameter.
I also see a scenario that the proposed patch does not handle well: The
Hello Will,
I have a patch for a ptrace(2) issue that we encountered on arm64 kernels.
If a debugger singlesteps a ptraced task, and then does a ptrace(2)
PTRACE_DETACH command, the task will not resume successfully. It seems
that clearing out the singlestep state, as something like a ptrace(2)
This short series fixes total breakage of Intel Atom PEBS support in recent
kernels.
The problems were introduced with the changes in the PEBS logic to handle
deeper buffer.
The first patch fixes PEBS and LBR problems, including NULL pointers, wrong
pointer
arithmetic, and wrong pebs record
On Wed, Sep 30, 2015 at 5:38 AM, Graeme Gregory
wrote:
> @@ -2368,18 +2368,28 @@ static int pl011_probe(struct amba_device *dev, const
> struct amba_id *id)
> if (!uap)
> return -ENOMEM;
>
> - uap->clk = devm_clk_get(>dev, NULL);
> - if (IS_ERR(uap->clk))
> -
This patches fixes a number of problems in the PEBS
and LBR support of Intel Atom. Those bugs were introduced
by the recent changes to the PEBS code to handle multiple
entries.
The kernel was assuming that if the CPU support 64-bit format
LBR, then it has an LBR_SELECT MSR. Atom uses 64-bit LBR
This patch updates the PEBS support for Intel Atom to provide
an alias for the cycles:pp event used by perf record/top by default
nowadays.
On Atom, only INST_RETIRED:ANY supports PEBS, so we use this event
instead with a large cmask to count cycles. Given that Core2 has
the same issue, we use
On Thu, Dec 03, 2015 at 02:56:37PM -0500, Waiman Long wrote:
> > #ifdef CONFIG_CGROUP_SCHED
> >+task_group_cache = KMEM_CACHE(task_group, 0);
> >+
> Thanks for making that change.
>
> Do we need to add the flag SLAB_HWCACHE_ALIGN? Or we could make a helper
> flag that define
The BCM6368 has a NAND interrupt register with combined status and enable
registers.
As the BCM6328, BCM6362 and BCM6368 all use v2.1 controllers, the first
variant that will work with this driver is the BCM63268 using a v4.0
controller.
Set up the device by disabling and acking all interrupts,
Attempt to enable a clock named "nand" as some SoCs have a clock for the
controller that needs to be enabled.
Signed-off-by: Simon Arlott
---
Removed ctrl->clk not NULL check.
drivers/mtd/nand/brcmnand/brcmnand.c | 64
1 file changed, 50 insertions(+), 14
From: Randy Dunlap
Fix 21 occurrences of this kernel-doc warning in :
..//include/crypto/aead.h:149: warning: No description found for parameter
'base'
Signed-off-by: Randy Dunlap
---
include/crypto/aead.h |1 +
1 file changed, 1 insertion(+)
--- lnx-44-rc3.orig/include/crypto/aead.h
Add device tree binding for NAND on the BCM6368.
The BCM6368 has a NAND interrupt register with combined status and enable
registers. It also requires a clock, so add an optional clock to the
common brcmnand binding.
Signed-off-by: Simon Arlott
---
.../devicetree/bindings/mtd/brcm,brcmnand.txt
On 12/03/2015 06:12 AM, Peter Zijlstra wrote:
I made this:
---
Subject: sched/fair: Move hot load_avg into its own cacheline
From: Waiman Long
Date: Wed, 2 Dec 2015 13:41:49 -0500
If a system with large number of sockets was driven to full
utilization, it was found that the clock tick
On Thu, Dec 03 2015 at 9:26am -0500,
Sami Tolvanen wrote:
> Changes since v1:
>
> - Added CONFIG_DM_VERITY_FEC and split error correction into
> dm-verity-fec.[ch] to further separate the functionality from the
> rest of dm-verity. Follows the same pattern as dm-uevent.
>
> -
Thanks for the detailed feedback and mentioning --strict option for
checkpatch :) I have fixed all the issues in the v2 version of the
patch: https://lkml.org/lkml/2015/12/3/606
On 12/02/2015 06:40 PM, Alexandre Belloni wrote:
On 11/11/2015 at 17:31:58 -0500, Akshay Bhat wrote :
diff --git
On 01.12.2015 23:02, Grant Grundler wrote:
> On Tue, Dec 1, 2015 at 12:44 PM, Helge Deller wrote:
>> On 01.12.2015 17:41, Bjorn Helgaas wrote:
>>> There are no callers of pcibios_init_bus(), so remove it.
>>
>> True, pcibios_init_bus() isn't called anywhere, so it should be removed.
>>
>> But I
On 12/03/2015 12:29 PM, Matwey V. Kornilov wrote:
> 2015-12-03 17:41 GMT+03:00 Peter Hurley :
>> Hi Matwey,
>>
>> On 12/03/2015 12:50 AM, Matwey V. Kornilov wrote:
>>> I am working on v4, where I completely redesigned implementation. And
>>> now I think that it is considerably better than v3.
>>>
Hello, Don.
On Thu, Dec 03, 2015 at 12:50:24PM -0500, Don Zickus wrote:
> This sort of looks like the hung task detector..
>
> I am a little concerned because we just made a big effort to properly
> separate the hardlockup and softlockup paths and yet retain the flexibility
> to enable/disable
On Thu, Dec 03, 2015 at 07:16:29PM +, Luck, Tony wrote:
> part4 (the actual KNL piece) seems not to break earlier (Broadwell)
> system ... but that doesn't qualify enough for Ack/Review/Tested -by.
It already has your Reviewed-by. Is it still valid?
--
Regards/Gruss,
Boris.
ECO tip
This driver supports the following functions:
- reading and setting time
- alarms when connected to an IRQ
- reading and clearing the voltage low flags
Datasheet:
http://www.epsondevice.com/docs/qd/en/DownloadServlet?id=ID000956
Signed-off-by: Akshay Bhat
---
Changes in v2:
- Address comments
On Thu, 03 Dec 2015, Peter Zijlstra wrote:
+/**
+ * smp_cond_acquire() - Spin wait for cond with ACQUIRE ordering
+ * @cond: boolean expression to wait for
+ *
+ * Equivalent to using smp_load_acquire() on the condition variable but employs
+ * the control dependency of the wait to reduce the
Waiman Long writes:
> On 12/02/2015 03:02 PM, bseg...@google.com wrote:
>> Waiman Long writes:
>>> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
>>> index efd3bfc..e679895 100644
>>> --- a/kernel/sched/sched.h
>>> +++ b/kernel/sched/sched.h
>>> @@ -248,7 +248,12 @@ struct task_group
On Thu, 2015-12-03 at 11:01 -0800, Linus Torvalds wrote:
> On Thu, Dec 3, 2015 at 10:40 AM, Borislav Petkov wrote:
> > On Thu, Dec 03, 2015 at 11:54:19AM -0700, Toshi Kani wrote:
> > > Adding a new type for regular memory will require inspecting the
> > > codes using IORESOURCE_MEM currently,
On 12/03/2015 05:56 AM, Peter Zijlstra wrote:
On Wed, Dec 02, 2015 at 01:41:49PM -0500, Waiman Long wrote:
+/*
+ * Make sure that the task_group structure is cacheline aligned when
+ * fair group scheduling is enabled.
+ */
+#ifdef CONFIG_FAIR_GROUP_SCHED
+static inline struct task_group
On Thu, 2015-12-03 at 04:02 -0600, Bucur Madalin-Cristian-B32716 wrote:
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Wednesday, December 02, 2015 11:41 PM
> >
> > On Mon, 2015-11-02 at 19:31 +0200, Madalin Bucur wrote:
> > > Allow the selection of the transmission queue
On 12/02/2015 11:32 PM, Mike Galbraith wrote:
On Wed, 2015-12-02 at 13:41 -0500, Waiman Long wrote:
By doing so, the perf profile became:
9.44% 0.00% java [kernel.vmlinux] [k] smp_apic_timer_interrupt
8.74% 0.01% java [kernel.vmlinux] [k] hrtimer_interrupt
7.83%
commit 65a124dd719d6e90591e4756bb04e1719489705e prevents WDS interface
type from bring brought up.
Simple Test:
before this you must have a AP interface, I used hostapd to create it so
I don't have a single liner to show that.
iw dev wlan0 interface add wlan0wds0 type wds
ip link set dev
On Fri, 2015-11-27 at 11:56 +0200, Andy Shevchenko wrote:
> > > > >
> On Fri, 2015-11-27 at 00:15 +0100, Rafael J. Wysocki wrote:
> > On Thursday, November 26, 2015 06:45:17 PM Andy Shevchenko wrote:
> > > On Thu, 2015-11-26 at 18:30 +0200, Jarkko Nikula wrote:
> > > > On 11/26/2015 05:19 PM,
On Thu, Dec 03, 2015 at 05:27:18PM +0100, Michal Hocko wrote:
> On Thu 03-12-15 22:16:55, Geliang Tang wrote:
> > To make the intention clearer, use list_{first,next}_entry instead
> > of list_entry.
>
> Does this really help readability? This function simply uncharges the
> given list of pages.
* Javier Martinez Canillas [151203 10:29]:
> Hello Tony,
>
> On 12/03/2015 03:16 PM, Tony Lindgren wrote:
> > * Javier Martinez Canillas [151203 10:03]:
> >> Hello,
> >>
> >> This series converts the IGEPv2 (IGEP0020) and IGEP COM Module (IGEP0030)
> >> Device Tree to use the MMC power sequence
Task or work item involved in memory reclaim trying to flush a
non-WQ_MEM_RECLAIM workqueue or one of its work items can lead to
deadlock. Trigger WARN_ONCE() if such conditions are detected.
Signed-off-by: Tejun Heo
Cc: Peter Zijlstra
---
Hello,
So, something like this. Seems to work fine
On 12/02/2015 03:02 PM, bseg...@google.com wrote:
Waiman Long writes:
If a system with large number of sockets was driven to full
utilization, it was found that the clock tick handling occupied a
rather significant proportion of CPU time when fair group scheduling
and autogroup were enabled.
The BCM6345 contains clocks gated with a register. Clocks are indexed
by bits in the register and are active high. Clock gate bits are
interleaved with other status bits and configurable clocks in the same
register.
Enabled by default for BMIPS_GENERIC.
Signed-off-by: Simon Arlott
---
Renamed
Hi, Thomas
On Commit 2a1d3ab8986d1b2 ("genirq: Handle force threading of irqs
with primary and thread handler"), even if the caller of
request_threaded_irq() provides a primary handler, that primary handler will
be invoked in thread context. This may cause some latency issue for high
Add device tree binding for the BCM6345's gated clocks.
The BCM6345 contains clocks gated with a register. Clocks are indexed
by bits in the register and are active high. Clock gate bits are
interleaved with other status bits and configurable clocks in the same
register.
Signed-off-by: Simon
Normally, when a user can modify a file that has setuid or setgid bits,
those bits are cleared when they are not the file owner or a member
of the group. This is enforced when using write and truncate but not
when writing to a shared mmap on the file. This could allow the file
writer to gain
* Grygorii Strashko [151203 10:18]:
> On 12/02/2015 01:38 AM, Tony Lindgren wrote:
>
> > Tony Lindgren (10):
> >ARM: OMAP2+: Fix timer entries for dm814x
> >clk: ti: Add few dm814x clock aliases
> >ARM: OMAP2+: Add DPPLS clock manager for dm814x
> >ARM: OMAP2+: Enable GPIO for
From: Eric Dumazet
User can pass an arbitrary large buffer to getdents().
It is typically a 32KB buffer used by libc scandir() implementation.
When scanning /proc/{pid}/fd, we can hold cpu way too long,
so add a cond_resched() to be kind with other tasks.
We've seen latencies of more than
2015-12-03 20:05 GMT+03:00 Johannes Berg :
> On Thu, 2015-12-03 at 18:50 +0300, Andrey Ryabinin wrote:
>> With upcoming CONFIG_UBSAN the following BUILD_BUG_ON in
>> net/mac80211/debugfs.c starts to trigger:
>> BUILD_BUG_ON(hw_flag_names[NUM_IEEE80211_HW_FLAGS] != (void
>> *)0x1);
>>
>> It
On 12/03/2015 12:29 PM, Heikki Krogerus wrote:
Several Intel PCHs and SOCs have an internal mux that is
used to share one USB port between USB Device Controller and
xHCI. The mux is normally handled by System FW/BIOS, but not
always. For those platforms where the FW does not take care
of the
> For patch 2 and 3 I'd need an ack from Mauro/Tony. CCed.
parts 2 & 3 are OK
Acked-by: Tony Luck
part4 (the actual KNL piece) seems not to break earlier (Broadwell) system ...
but that doesn't qualify enough for Ack/Review/Tested -by.
-Tony
On Thu, 03 Dec 2015 10:36:18 -0800
"Shi, Yang" wrote:
> > called directly that calls these functions internally and the tracepoint
> > can trap the return value.
>
> This will incur more changes in other subsystems (futex, kvm, etc), I'm
> not sure if it is worth making such changes to get
Hello.
On 12/03/2015 12:29 PM, Heikki Krogerus wrote:
Intel Braswell/Cherrytrail has an internal mux that shares
one USB port between USB Device Controller and xHCI. The
same mux is found on several SOCs from Intel, but only on
a few Cherrytrail based platforms the OS is expected to
configure
On Thu, Dec 3, 2015 at 10:40 AM, Borislav Petkov wrote:
> On Thu, Dec 03, 2015 at 11:54:19AM -0700, Toshi Kani wrote:
>> Adding a new type for regular memory will require inspecting the codes
>> using IORESOURCE_MEM currently, and modify them to use the new type if
>> their target ranges are
On Thu, 3 Dec 2015 19:42:41 +0100
Borislav Petkov wrote:
> No, those are going away:
>
> https://lkml.kernel.org/r/1448982023-19187-4-git-send-email...@alien8.de
>
> Next on my TODO is killing the rest of them.
Fair enough.
Acked-by: Jacob Pan
--
To unsubscribe from this list: send the line
On 03/12/15 18:13, Tony Lindgren wrote:
* Linus Walleij [151201 06:07]:
On Fri, Nov 27, 2015 at 6:21 PM, Sudeep Holla wrote:
From: Sudeep Holla
The IRQF_NO_SUSPEND flag is used to identify the interrupts that should
be left enabled so as to allow them to work as expected during the
The ACPI compiler uses the extended format when used interrupt numbers
are greater than 15. The extended IRQ is 32 bits according to the ACPI
spec. The code supports parsing the extended interrupt numbers. However,
due to used data structure type; the code silently truncates interrupt
numbers
On Thu, 2015-12-03 at 10:22 -0800, Yunhong Jiang wrote:
> When assigning a VFIO device to a KVM guest with low latency requirement, it
> is better to handle the interrupt in the hard interrupt context, to reduce
> the context switch to/from the IRQ thread.
>
> Based on discussion on
David Miller writes:
> From: Robert Jarzmik
> Date: Mon, 30 Nov 2015 22:40:28 +0100
>
>> Convert the dma transfers to be dmaengine based, now pxa has a dmaengine
>> slave driver. This makes this driver a bit more PXA agnostic.
>>
>> The driver was only compile tested. The risk is quite small
On Thu, Dec 03, 2015 at 10:38:28AM -0800, Jacob Pan wrote:
> or use this?
> #define cpu_has_hypervisorboot_cpu_has(X86_FEATURE_HYPERVISOR)
No, those are going away:
https://lkml.kernel.org/r/1448982023-19187-4-git-send-email...@alien8.de
Next on my TODO is killing the rest of them.
--
On Thu, Dec 03, 2015 at 11:54:19AM -0700, Toshi Kani wrote:
> Adding a new type for regular memory will require inspecting the codes
> using IORESOURCE_MEM currently, and modify them to use the new type if
> their target ranges are regular memory. There are many references to this
> type across
On 11/30/2015 11:45 PM, Ken Xue wrote:
The routines in scsi_pm.c assume that if a runtime-PM callback is
invoked for a SCSI device, it can only mean that the device's driver
has asked the block layer to handle the runtime power management (by
calling blk_pm_runtime_init(), which among other
On Thu, 3 Dec 2015 19:27:02 +0100
Borislav Petkov wrote:
>
> + if (boot_cpu_has(X86_FEATURE_HYPERVISOR))
> + return 0;
> +
or use this?
#define cpu_has_hypervisor boot_cpu_has(X86_FEATURE_HYPERVISOR)
--
To unsubscribe from this list: send the line "unsubscribe
Separate the irqfd_wakeup_pollin/irqfd_wakeup_pollup from the
irqfd_wakeup, so that we can reuse the logic for MSI fastpath injection.
Signed-off-by: Yunhong Jiang
---
virt/kvm/eventfd.c | 86 --
1 file changed, 51 insertions(+), 35
For VFIO device with MSI interrupt type, it's possible to handle the
interrupt on hard interrupt context without invoking the interrupt
thread. Handling the interrupt on hard interrupt context reduce the
interrupt latency.
Signed-off-by: Yunhong Jiang
---
drivers/vfio/pci/vfio_pci_intrs.c | 39
> On Dec 3, 2015, at 00:03, Rasmus Villemoes wrote:
>
> On Thu, Dec 03 2015, yalin wang wrote:
>
>>> On Dec 2, 2015, at 13:04, Vlastimil Babka wrote:
>>>
>>> On 12/02/2015 06:40 PM, yalin wang wrote:
>>>
>>> (please trim your reply next time, no need to quote whole patch here)
>>>
i
Add an irq_bypass consumer to the KVM eventfd, so that when a MSI interrupt
happens and triggerred from VFIO, it can be handled fast.
Signed-off-by: Yunhong Jiang
---
include/linux/kvm_irqfd.h | 1 +
virt/kvm/eventfd.c| 42 ++
2 files changed, 43
Extend the irq_bypass manager to support runtime consumers. A runtime
irq_bypass consumer can handle interrupt when an interrupt triggered. A
runtime consumer has it's handle_irq() function set and passing a
irq_context for the irq handling.
A producer keep a link for the runtime consumers, so
On 12/2/2015 8:07 PM, Steven Rostedt wrote:
On Wed, 2 Dec 2015 14:53:27 -0800
Yang Shi wrote:
page-faults events record the invoke to handle_mm_fault, but the invoke
may come from do_page_fault or gup. In some use cases, the finer event count
mey be needed, so add trace events support for:
When assigning a VFIO device to a KVM guest with low latency requirement, it
is better to handle the interrupt in the hard interrupt context, to reduce
the context switch to/from the IRQ thread.
Based on discussion on https://lkml.org/lkml/2015/10/26/764, the VFIO msi
interrupt is changed to
The x86 support setting irq in atomic, expose it to vfio driver.
Signed-off-by: Yunhong Jiang
---
arch/x86/kvm/Kconfig | 1 +
include/linux/kvm_host.h | 19 ---
virt/kvm/Kconfig | 3 +++
virt/kvm/eventfd.c | 9 -
4 files changed, 20 insertions(+), 12
On 12/2/2015 8:13 PM, Steven Rostedt wrote:
On Wed, 2 Dec 2015 15:36:50 -0800
Dave Hansen wrote:
On 12/02/2015 02:53 PM, Yang Shi wrote:
diff --git a/mm/gup.c b/mm/gup.c
index deafa2c..10245a4 100644
--- a/mm/gup.c
+++ b/mm/gup.c
@@ -13,6 +13,9 @@
#include
#include
+#define
On 12/03/2015 08:13 PM, Tony Lindgren wrote:
> * Linus Walleij [151201 06:07]:
>> On Fri, Nov 27, 2015 at 6:21 PM, Sudeep Holla wrote:
>>
>>> From: Sudeep Holla
>>>
>>> The IRQF_NO_SUSPEND flag is used to identify the interrupts that should
>>> be left enabled so as to allow them to work as
Hi Noam,
On 02/12/15 15:08, Noam Camus wrote:
>> From: Marc Zyngier [mailto:marc.zyng...@arm.com]
>> Sent: Tuesday, December 01, 2015 3:29 PM
>
>> + interrupt source. The value shall be 1.
>
>> So you never have to encode the interrupt trigger type? Do you only support
>> edge or level?
> I
Hello Tony,
On 12/03/2015 03:16 PM, Tony Lindgren wrote:
> * Javier Martinez Canillas [151203 10:03]:
>> Hello,
>>
>> This series converts the IGEPv2 (IGEP0020) and IGEP COM Module (IGEP0030)
>> Device Tree to use the MMC power sequence provider to initialize the SDIO
>> WiFi chip instead of
On Thu, 3 Dec 2015, Russell King - ARM Linux wrote:
> On Thu, Dec 03, 2015 at 04:41:18PM +, Russell King - ARM Linux wrote:
> > On Thu, Dec 03, 2015 at 04:12:06PM +, Peter Rosin wrote:
> > > * uaccess_with_memcpy.c:__copy_to_user() has a mode in which it copies
> > > "non-atomically"
From: Borislav Petkov
qemu/kvm doesn't support RAPL and RAPL doesn't have a CPUID feature bit
so check whether we're in a guest instead.
Reported-by: Hannes Reinecke
Signed-off-by: Borislav Petkov
Cc: Arnaldo Carvalho de Melo
Cc: "H. Peter Anvin"
Cc: Ingo Molnar
Cc: Jacob Pan
Cc: Peter
Peter Zijlstra writes:
> On Thu, Dec 03, 2015 at 09:56:02AM -0800, bseg...@google.com wrote:
>> Peter Zijlstra writes:
>
>> > @@ -7402,11 +7405,12 @@ void __init sched_init(void)
>> > #endif /* CONFIG_RT_GROUP_SCHED */
>> >
>> > #ifdef CONFIG_CGROUP_SCHED
>> > + task_group_cache =
On Fri, Nov 27, 2015 at 09:52:16AM +0800, Xishi Qiu wrote:
> On 2015/11/26 23:49, Mark Rutland wrote:
>
> > On Thu, Nov 26, 2015 at 11:05:32PM +0800, zhong jiang wrote:
> >> On 2015/11/25 23:04, Mark Rutland wrote:
> >>> On Wed, Nov 25, 2015 at 09:41:12PM +0800, zhongjiang wrote:
> This
On Thu, Dec 03, 2015 at 08:00:42AM +0200, Jarkko Sakkinen wrote:
> I guess it'd be more realiable. In my NUC the current fix works and the
> people who tested it. If you supply me a fix that changes it to use that
> I can test it and this will give also coverage to the people who tested
> my
On Thu, Dec 3, 2015 at 4:36 AM, Peter Zijlstra wrote:
>
> I've edited the changelog like so, please let me know if that is fine
> with you.
Ack.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
301 - 400 of 1804 matches
Mail list logo
