There are some places inside RCU core, where we need to iterate all mask
(->qsmask, ->expmask, etc) bits in a leaf node, in order to iterate all
corresponding CPUs. The current code iterates all possible CPUs in this
leaf node and then checks with the mask to see whether the bit is set.
However, g
sound/soc/codecs/wm0010.c does not use any miscdevice so this patch
remove this unnecessary inclusion.
Signed-off-by: Corentin Labbe
---
sound/soc/codecs/wm0010.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/codecs/wm0010.c b/sound/soc/codecs/wm0010.c
index 0eb5dcf..4f5f571 10064
On 12/14/2016 03:30 PM, Greg KH wrote:
On Wed, Dec 14, 2016 at 12:20:50PM -0800, Mark Salyzyn wrote:
On 12/13/2016 04:00 PM, Greg KH wrote:
On Tue, Dec 13, 2016 at 03:42:58PM -0800, Mark Salyzyn wrote:
On 12/12/2016 10:26 PM, Cong Wang wrote:
On Mon, Dec 12, 2016 at 4:26 PM, Mark Salyzyn wro
On Thu, 2016-12-15 at 07:15 +0200, Michael S. Tsirkin wrote:
> __bitwise__ is an implementation detail now.
Assuming the other patches go in, thanks.
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index fd3556b..982c52c 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpat
sound/soc/codecs/rt5677-spi.c does not use any miscdevice so this patch
remove this unnecessary inclusion.
Signed-off-by: Corentin Labbe
---
sound/soc/codecs/rt5677-spi.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/codecs/rt5677-spi.c b/sound/soc/codecs/rt5677-spi.c
index ebd0f7
sound/soc/codecs/rt5514-spi.c does not use any miscdevice so this patch
remove this unnecessary inclusion.
Signed-off-by: Corentin Labbe
---
sound/soc/codecs/rt5514-spi.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/codecs/rt5514-spi.c b/sound/soc/codecs/rt5514-spi.c
index 0901e2
Signed-off-by: Loic Pallardy
---
drivers/mailbox/mailbox-sti.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mailbox/mailbox-sti.c b/drivers/mailbox/mailbox-sti.c
index a334db5..41bcd33 100644
--- a/drivers/mailbox/mailbox-sti.c
+++ b/drivers/mailbox/mailbox-sti.c
@@ -403,6 +403,7 @
Linus,
This release has a few updates:
o STM can hook into the function tracer
o Function filtering now supports more advance glob matching
o Ftrace selftests updates and added tests
o Softirq tag in traces now show only softirqs
o ARM nop added to non traced locations at compile time
o Ne
When VDMA is configured for more than one frame in the h/w
for example h/w is configured for n number of frames and user
Submits n number of frames and triggered the DMA using issue_pending API.
In the current driver flow we are submitting one frame at a time
but we should submit all the n number o
This patch series fixes below bugs in DMA and VDMA IP's
---> Do not start VDMA until frame buffer is processed by the h/w
---> Fix bug in Multi frame sotres handling in VDMA
---> Fix issues w.r.to multi frame descriptors submit with AXI DMA S2MM(recv)
Side.
Kedareswara rao Appana (3):
dmaengin
When driver is handling AXI DMA SoftIP
When user submits multiple descriptors back to back on the S2MM(recv)
side with the current driver flow the last buffer descriptor next bd
points to a invalid location resulting the invalid data or errors in the
DMA engine.
This patch fixes this issue by crea
hid/intel-ish-hid does not use any miscdevice so this patch remove
this unnecessary inclusion.
Signed-off-by: Corentin Labbe
---
drivers/hid/intel-ish-hid/ipc/pci-ish.c | 1 -
drivers/hid/intel-ish-hid/ishtp/hbm.c | 1 -
drivers/hid/intel-ish-hid/ishtp/init.c | 1 -
3 files changed, 3 deletio
While testing Joe's conversion of samples/bpf/ to use tools/lib/bpf/ I
noticed some warnings, do you guys mind if I put patches like the one
below in my tree, pushing to Ingo soon?
Or is there anything subtle against doing so?
While building samples/bpf/ on a Fedora Rawhide container, wit
On Wed, Dec 14, 2016 at 12:18:53PM +0100, Geert Uytterhoeven wrote:
> With gcc 4.1.2:
>
> drivers/usb/serial/f81534.c: In function ‘f81534_port_probe’:
> drivers/usb/serial/f81534.c:1250: warning: comparison is always false due
> to limited range of data type
>
> f81534_logic_to_phy_port
Hello,
Thanks for this review, it will help.
2016-12-13 10:20 GMT+01:00 Uwe Kleine-König :
> Hello,
>
> On Mon, Dec 12, 2016 at 05:15:39PM +0100, M'boumba Cedric Madianga wrote:
>> This patch adds support for the STM32F4 I2C controller.
>>
>> Signed-off-by: M'boumba Cedric Madianga
>> ---
>> dr
On Thu, Dec 15, 2016 at 11:21:05PM +0800, Boqun Feng wrote:
> There are some places inside RCU core, where we need to iterate all mask
> (->qsmask, ->expmask, etc) bits in a leaf node, in order to iterate all
> corresponding CPUs. The current code iterates all possible CPUs in this
> leaf node and
Hi Kedar,
On 15-12-2016 15:19, Appana Durga Kedareswara Rao wrote:
> Hi Jose Abreu,
>
> Thanks for the patch...
>
>> Xilinx VDMA supports multiple framebuffers. This patch adds correct handling
>> for
>> the scenario where multiple framebuffers are available in the HW and parking
>> mode i
On 12/14/2016 12:59 AM, Li, Liang Z wrote:
>> Subject: Re: [Qemu-devel] [PATCH kernel v5 0/5] Extend virtio-balloon for
>> fast (de)inflating & fast live migration
>>
>> On 12/08/2016 08:45 PM, Li, Liang Z wrote:
>>> What's the conclusion of your discussion? It seems you want some
>>> statistic bef
On Thu Dec 15 09:18:44 2016 Kalle Valo wrote:
> (Adding Luis because he has been working on request_firmware() lately)
>
> Pali Rohár writes:
>
> > > > So no, there is no argument against... request_firmware() in
> > > > fallback mode with userspace helper is by design blocking and
> > > > wait
On Wed, Dec 14, 2016 at 11:17:16AM -0500, Steven Rostedt wrote:
>
> [ added the forgotten LKML ;-) ]
Thanks! :)
>
> On Wed, 14 Dec 2016 09:53:01 -0500
> Steven Rostedt wrote:
>
> > On Wed, 14 Dec 2016 16:13:51 +0900
> > Namhyung Kim wrote:
> >
> > > Hi Steve,
> > >
> > > While looking at t
Em Thu, Dec 15, 2016 at 11:33:29AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Dec 14, 2016 at 02:46:23PM -0800, Joe Stringer escreveu:
> > On 14 December 2016 at 06:55, Arnaldo Carvalho de Melo
> > wrote:
> > > So, Joe, can you try refreshing this work, starting from what I have in
> > >
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Vitaly Kuznetsov
> Sent: Wednesday, April 20, 2016 21:48
> To: Ming Lei
> Cc: Keith Busch ; linux-bl...@vger.kernel.org; Linux
> Kernel Mailing List ; Jens Axboe
> ; Dan Williams ; Martin K.
> Pe
I was going to do some measurements but my kernel crashes now with a
page fault in efi_rtc_probe():
[ 21.663393] Unable to handle kernel paging request at virtual address
20251000
[ 21.663396] pgd = 0909
[ 21.663401] [20251000] *pgd=01090003
[ 21.663402] , *pud=010
From: Hannes Frederic Sowa
> Sent: 15 December 2016 14:57
> On 15.12.2016 14:56, David Laight wrote:
> > From: Hannes Frederic Sowa
> >> Sent: 15 December 2016 12:50
> >> On 15.12.2016 13:28, David Laight wrote:
> >>> From: Hannes Frederic Sowa
> Sent: 15 December 2016 12:23
> >>> ...
> H
On Fri, Dec 16, 2016 at 12:32 AM, Namhyung Kim wrote:
> On Wed, Dec 14, 2016 at 11:17:16AM -0500, Steven Rostedt wrote:
>> @@ -203,8 +212,13 @@ static int get_sample(void)
>> }
>> if (diff > outer_sample)
>> outer_sample = d
On 12/14/2016 3:28 PM, Mathias Nyman wrote:
On 14.12.2016 12:58, Michal Necasek wrote:
prior to the endpoint reset. SetFeature(CLEAR_HALT) resets the toggle
on the device, but not on the host. But we know for a fact that the
device sends a packet (with data toggle 0) which the host USB stack
nev
Thanks Greg. I have send another patch with changes as per your suggestions.
Please review it and let me know if you have any concerns.
- Manish
-Original Message-
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Thursday, December 15, 2016 2:29 AM
To: Manish Narani
Cc: mathias.n
On Wed, Dec 14, 2016 at 08:32:39PM +0100, Peter Zijlstra wrote:
> On Wed, Dec 14, 2016 at 07:16:36PM +0100, Jiri Olsa wrote:
>
> > > > +++ b/arch/x86/events/intel/ds.c
> > > > @@ -1389,9 +1389,13 @@ static void intel_pmu_drain_pebs_nhm(struct
> > > > pt_regs *iregs)
> > > >
On Thu Dec 15 15:46:28 2016 Michał Kępień wrote:
> > On Thursday 08 December 2016 13:36:14 Michał Kępień wrote:
> > > --- a/sound/pci/hda/dell_wmi_helper.c
> > > +++ b/sound/pci/hda/dell_wmi_helper.c
> > > @@ -6,7 +6,7 @@
> > > #include
> > >
> > > static int dell_led_value;
> > > -static int (*
Add channel idle state to ensure that dma descriptor is not
submitted when VDMA engine is in progress.
Signed-off-by: Kedareswara rao Appana
---
drivers/dma/xilinx/xilinx_dma.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/dma/xilinx/xilinx_dma.c b/drivers/dma/xilinx/xilin
On Thu, 2016-12-15 at 16:19 +0100, Corentin Labbe wrote:
> sound/soc/codecs/wm0010.c does not use any miscdevice so this patch
> remove this unnecessary inclusion.
>
> Signed-off-by: Corentin Labbe
> ---
> sound/soc/codecs/wm0010.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/sound/s
Hi Kedar,
On 15-12-2016 15:11, Kedareswara rao Appana wrote:
> Add channel idle state to ensure that dma descriptor is not
> submitted when VDMA engine is in progress.
>
> Signed-off-by: Kedareswara rao Appana
> ---
> drivers/dma/xilinx/xilinx_dma.c | 9 +
> 1 file changed, 9 insertions
Hi Jose Abreu,
Thanks for the patch...
I have just posted different patch series for fixing these issues just
now...
Please take a look into it...
Regards,
Kedar.
> Subject: [PATCH] dmaengine: xilinx_dma: Add support for multiple buffers
>
> Xilinx VDMA supports multiple frame
On 12/15/2016 04:29 PM, Arnaldo Carvalho de Melo wrote:
While testing Joe's conversion of samples/bpf/ to use tools/lib/bpf/ I
noticed some warnings, do you guys mind if I put patches like the one
below in my tree, pushing to Ingo soon?
Or is there anything subtle against doing so?
Fwiw, no o
Em Wed, Dec 14, 2016 at 02:43:39PM -0800, Joe Stringer escreveu:
> Now that libbpf under tools/lib/bpf/* is synced with the version from
> samples/bpf, we can get rid most of the libbpf library here.
>
> Signed-off-by: Joe Stringer
> Cc: Alexei Starovoitov
> Cc: Daniel Borkmann
> Cc: Wang Nan
On 14.12.2016 23:12, Sasikumar Chandrasekaran wrote:
> Sasikumar Chandrasekaran (11):
> megaraid_sas: Add new pci device Ids for SAS3.5 Generic Megaraid
> Controllers
> megaraid_sas: 128 MSIX Support
> megaraid_sas: EEDP Escape Mode Support for SAS3.5 Generic Megaraid
> Controllers
>
Hi Andi,
This patch breaks all rc devices, none of them have input devices any
more (see below).
On Wed, Dec 14, 2016 at 11:00:26PM +0900, Andi Shyti wrote:
> Move the input device allocation, map and protocol handling to
> different functions.
>
> Signed-off-by: Andi Shyti
> Reviewed-by: Sean
On 15-Dec-16 15:17, Peter Rosin wrote:
> On 2016-12-15 15:38, Luis Oliveira wrote:
>> diff --git a/drivers/i2c/busses/i2c-designware-core.h
>> b/drivers/i2c/busses/i2c-designware-core.h
>> index 26250b425e2f..3cb81fca7738 100644
>> --- a/drivers/i2c/busses/i2c-designware-core.h
>> +++ b/drivers/i2
On 15.12.2016 16:41, David Laight wrote:
> Try (retyped):
>
> echo 'struct { long a; long long b; } s; int bar { return sizeof s; }' >foo.c
> gcc [-m32] -O2 -S foo.c; cat foo.s
>
> And look at what is generated.
I used __alignof__(unsigned long long) with -m32.
>> Right now ipv6 addresses have
Em Thu, Dec 15, 2016 at 04:49:07PM +0100, Daniel Borkmann escreveu:
> On 12/15/2016 04:29 PM, Arnaldo Carvalho de Melo wrote:
> >
> > While testing Joe's conversion of samples/bpf/ to use tools/lib/bpf/ I
> > noticed some warnings, do you guys mind if I put patches like the one
> > below in my tre
On 11/07/2016 05:31 PM, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake "Obselete" to "Obsolete"
> in error message and also turn multi-line text into one
> line.
Thanks for the patch. It has been applied on my for-v4.10 branch.
Bart.
On Thu, Dec 15, 2016 at 07:34:33AM -0800, Dave Hansen wrote:
> On 12/14/2016 12:59 AM, Li, Liang Z wrote:
> >> Subject: Re: [Qemu-devel] [PATCH kernel v5 0/5] Extend virtio-balloon for
> >> fast (de)inflating & fast live migration
> >>
> >> On 12/08/2016 08:45 PM, Li, Liang Z wrote:
> >>> What's th
From: Yegor Yefremov
Signed-off-by: Yegor Yefremov
---
Documentation/devicetree/bindings/usb/ehci-omap.txt | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/usb/ehci-omap.txt
b/Documentation/devicetree/bindings/usb/ehci-omap.txt
index 3dc231c..d77e11a 100644
From: Yegor Yefremov
OMAP related files are actually named ehci-omap.txt and ohci-omap3.txt.
Also add full path to ohci-omap3.txt.
Signed-off-by: Yegor Yefremov
---
Documentation/devicetree/bindings/mfd/omap-usb-host.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/
Linus,
The following changes since commit 6a34e4d2be07255cc59e6ccaf820669cfd7f815c:
fscrypt: Rename FS_WRITE_PATH_FL to FS_CTX_HAS_BOUNCE_BUFFER_FL (2016-12-11
16:33:18 -0500)
are available in the git repository at:
git://git.infradead.org/linux-ubifs.git tags/upstream-4.10-rc1
for you to
On 15.12.16 11:01:04, Yisheng Xie wrote:
> > I sent a V2 patch that uses pfn_present(). This only initilizes
> > sections with memory.
> hmm， maybe I do not quite catch what your mean, but I do not think
> pfn_present is right for this case.
>
> IMO, The valid_section() means the section with mem_
On 15 December 2016 at 15:39, Robert Richter wrote:
> I was going to do some measurements but my kernel crashes now with a
> page fault in efi_rtc_probe():
>
> [ 21.663393] Unable to handle kernel paging request at virtual address
> 20251000
> [ 21.663396] pgd = 0909
> [ 21.6634
Hi Linus:
This push fixes the following issues:
- A crash regression in the new skcipher walker.
- Incorrect return value in public_key_verify_signature.
- Fix for in-place signing in the sign-file utility.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git l
On Thu, Dec 15, 2016 at 08:09:16PM +0530, Tabrez Khan wrote:
> On Thu, Dec 15, 2016 at 7:08 AM, Greg KH wrote:
> > On Thu, Dec 15, 2016 at 07:03:52AM +0530, Tabrez khan wrote:
> >> Remove unnecessary braces {} for single if statement block.
> >> This warning is found using checkpatch.pl.
> >>
> >>
Hi Kedar,
On 15-12-2016 15:11, Kedareswara rao Appana wrote:
> When VDMA is configured for more than one frame in the h/w
> for example h/w is configured for n number of frames and user
> Submits n number of frames and triggered the DMA using issue_pending API.
> In the current driver flow we are
Boris,
with today's kernel the system isn't coming up when booted as Xen dom0:
[ 33.575326] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s!
[swapper/0:1]
[ 33.589795] Modules linked in:
[ 33.596015] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-pv+ #687
[ 33.608844] Hardware name:
On Thu, Dec 15, 2016 at 3:40 AM, Weilong Chen wrote:
> Nessus report the vf appears to leak memory in network packets.
> Fix this by padding all small packets manually.
>
> And the CVE-2003-0001.
> https://ofirarkin.files.wordpress.com/2008/11/atstake_etherleak_report.pdf
>
> Signed-off-by: Weilon
This reverts commit 49fd897573c97b0eaf10f47d850027d78c456cd7.
Reverting back to commit 0549a3c because the values are used by crash
and other tools already. I expected this commit would not go through given
the unresolved comments. I want it to be easy to resolve major memory
section positions whe
Hi.
Per Documentation/DMA-API-HOWTO.txt, driver of device capable of 64-bit
DMA addressing, should call dma_set_mask_and_coherent(dev,
DMA_BIT_MASK(64)) and if that succeeds, assume that 64-bit DMA
addressing is available.
This behaves incorrectly on arm64 system (Renesas r8a7795-h3ulcb) here.
-
On Thu, 2016-12-15 at 16:27 +0100, Corentin Labbe wrote:
> hid/intel-ish-hid does not use any miscdevice so this patch remove
> this unnecessary inclusion.
>
> Signed-off-by: Corentin Labbe
Acked-by: Srinivas Pandruvada
> ---
> drivers/hid/intel-ish-hid/ipc/pci-ish.c | 1 -
> drivers/hid/intel
On Thu 2016-12-15 13:53:58, Geert Uytterhoeven wrote:
> If CONFIG_PRINTK=n:
>
> kernel/printk/printk.c:1893: warning: ‘cont’ defined but not used
>
> Note that there are actually two different struct cont definitions and
> objects: the first one is used if CONFIG_PRINTK=y, the second one beca
On 12/15/2016 06:26 AM, Jens Axboe wrote:
> We never change it, make that clear.
Reviewed-by: Bart Van Assche
On Thursday, December 15, 2016 4:47 AM, Ian Abbott wrote:
> On 14/12/16 16:14, Hartley Sweeten wrote:
>> On December 14, 2016 6:42 AM, Piotr Gregor wrote:
>>> -struct pci_dev *comedi_to_pci_dev(struct comedi_device *);
>>> +struct pci_dev *comedi_to_pci_dev(struct comedi_device *dev);
>>
>> For the
On 12/15/2016 3:40 AM, Michael Kerrisk (man-pages) wrote:
> Hello all,
>
> Because the topic every now then comes up "which capability
> should I associate with the new feature that I'm adding to
> the kernel?", I propose to add the text below to the
> capabilities(7) man page [1] with some reco
On 12/14/2016 5:56 AM, Stephen Boyd wrote:
> On 12/12, Imran Khan wrote:
>> The SoC info driver provides information such as Chip ID,
>> Chip family, serial number and other such details about
>> Qualcomm SoCs.
>
> Yes but why do we care?
>
We intend to expose some standard SoC attributes (like s
Add support for an optional over current input pin which
can be used to send an over current event to the regulator
consumer.
Cc: devicet...@vger.kernel.org
Acked-by: Rob Herring
Signed-off-by: Axel Haslam
---
Documentation/devicetree/bindings/regulator/fixed-regulator.txt | 2 ++
1 file change
On Thu 15-12-16 07:22:30, Mark Salyzyn wrote:
> On 12/14/2016 03:30 PM, Greg KH wrote:
> >On Wed, Dec 14, 2016 at 12:20:50PM -0800, Mark Salyzyn wrote:
> >>On 12/13/2016 04:00 PM, Greg KH wrote:
> >>>On Tue, Dec 13, 2016 at 03:42:58PM -0800, Mark Salyzyn wrote:
> On 12/12/2016 10:26 PM, Cong Wa
> > + /* rc_open will be called here */
> > + rc = input_register_device(dev->input_dev);
> > + if (rc)
> > + goto out_table;
> > +
> > + dev->input_dev->dev.parent = &dev->dev;
> > + memcpy(&dev->input_dev->id, &dev->input_id, sizeof(dev->input_id));
> > + dev->input_dev->phy
Looks fine
-- james
Signed-off-by: James Smart
On 12/15/2016 5:20 AM, Johannes Thumshirn wrote:
Simplify the error handling of nvme_fc_create_hw_io_queues(), this saves us
one variable and one level of indentation.
Signed-off-by: Johannes Thumshirn
---
drivers/nvme/host/fc.c | 15 +
Some usb drivers rely on external power switches/regulators
for the port vbus, and some of these drivers are still using
a plain gpio to control the enable and over current
indicator pins.
To make these drivers more generic, we can use a regulator
to handle vbus, and send and over current event, b
Fixed regulators (ex. TPS2087D) may have a over current pin that
is activated on over current. Consumers may be interested to know
about over current events to take appropriate actions.
Allow the fix regulator to take in an optional gpio pin for over
current and send the respective event to the co
On Thu, Dec 15, 2016 at 01:08:51AM +, Gonglei (Arei) wrote:
>
>
>
>
> Regards,
> -Gonglei
>
>
> > -Original Message-
> > From: Zeng, Xin [mailto:xin.z...@intel.com]
> > Sent: Thursday, December 15, 2016 8:59 AM
> > To: Gonglei (Arei); Halil Pasic; linux-kernel@vger.kernel.org;
> >
Hi,
On Wed, Dec 14, 2016 at 10:41 PM, Frank Wang wrote:
> Hi Brain, Doug and Heiko,
>
> I would like to summarize why this story was constructed.
>
> The ehci/ohci-platform suspend process are blocked due to UTMI clock which
> directly output from usb-phy has been disabled, and why the UTMI clock
When the kernel is compiled with an "O=" argument, the object files are
not necessarily in the source tree, and more probably in another tree.
In this situation, the current used check doesn't work, and
COMPILED_SOURCE tags is broken with O= builds.
This patch fixes it by looking for object files
GCC generates lousy code in __switch_to_extra(). Aside of that some of the
operations there are implemented suboptimal.
This series, inspired by a patch from Kyle, helps the compiler to be less
stupid by explicitely giving the hints to optimize and replaces the open
coded bit toggle mechanisms wit
Provide and use a seperate helper for toggling the DEBUGCTLMSR_BTF bit
instead of doing it open coded with a branch and eventually evaluating
boot_cpu_data twice.
x86_64:
3694 8505 16 122152fb7 Before
3662 8505 16 121832f97 After
i386:
5986 93881804 1
Provide and use a toggle helper instead of doing it with a branch.
x86_64:
3662 8505 16 121832f97 Before
3646 8505 16 121672f87 After
i386:
5906 93881804 1709842ca Before
5834 93241740 168984202 After
Signed-off-by: Thomas Gleixn
On Thu, Dec 15, 2016 at 05:12:04PM +0100, Juergen Gross wrote:
> with today's kernel the system isn't coming up when booted as Xen dom0:
Remind me again pls, is dom0 even supposed to load microcode? Isn't the
hypervisor supposed to apply microcode?
> Looking into the state of cpu 1 I find the fol
Help the compiler to avoid reevaluating the thread flags for each checked
bit by reordering the bit checks and providing an explicit xor for
evaluation.
x8664: arch/x86/kernel/process.o
text data bss dec hex
3726 8505 16 122472fd7 Before
3694 8505 16
Hi, Dan,
Dan Williams writes:
> On Tue, Dec 13, 2016 at 3:46 PM, Jeff Moyer wrote:
>> Hi, Dan,
>>
>> In general, I have a couple of concerns with this patchset:
>> 1) You're making a case that subdivision shouldn't be persistent, which
>>means that all of the code we already have for subdiv
On Thu, 15 Dec 2016, Boris Ostrovsky wrote:
> Since cpu hotplug callbacks are requested for CPUHP_AP_ONLINE_DYN state,
> successful callback initialization will result in cpuhp_setup_state()
> returning a positive value. Therefore acpi_cpufreq_online being zero
> indicates that callbacks have not
On 2016-12-15 15:38, Luis Oliveira wrote:
> diff --git a/drivers/i2c/busses/i2c-designware-core.h
> b/drivers/i2c/busses/i2c-designware-core.h
> index 26250b425e2f..3cb81fca7738 100644
> --- a/drivers/i2c/busses/i2c-designware-core.h
> +++ b/drivers/i2c/busses/i2c-designware-core.h
> @@ -36,7 +36,
Gentle ping ...
Vincent
On 1 December 2016 at 17:38, Vincent Guittot wrote:
> The update of the share of a cfs_rq is done when its load_avg is updated
> but before the group_entity's load_avg has been updated for the past time
> slot. This generates wrong load_avg accounting which can be signifi
>>> On 15.12.16 at 17:46, wrote:
> On Thu, Dec 15, 2016 at 05:12:04PM +0100, Juergen Gross wrote:
>> with today's kernel the system isn't coming up when booted as Xen dom0:
>
> Remind me again pls, is dom0 even supposed to load microcode? Isn't the
> hypervisor supposed to apply microcode?
Yes,
On Thu 2016-12-08 11:49:20, Luis R. Rodriguez wrote:
> This adds helpers for getting access to the kmod count and limit from
> userspace. While at it, this also lets userspace fine tune the kmod
> limit after boot, it uses the shiny new proc_douintvec_minmax().
>
> These knobs should help userspac
Commit-ID: 512f09801b356c54baef62543e51169f03b2e642
Gitweb: http://git.kernel.org/tip/512f09801b356c54baef62543e51169f03b2e642
Author: Boris Ostrovsky
AuthorDate: Thu, 15 Dec 2016 10:00:57 -0500
Committer: Thomas Gleixner
CommitDate: Thu, 15 Dec 2016 17:48:20 +0100
cpu/hotplug: Clarify
On 12/15/2016 11:46 AM, Borislav Petkov wrote:
> On Thu, Dec 15, 2016 at 05:12:04PM +0100, Juergen Gross wrote:
>> with today's kernel the system isn't coming up when booted as Xen dom0:
> Remind me again pls, is dom0 even supposed to load microcode? Isn't the
> hypervisor supposed to apply microco
On 15/12/16 16:53, Jan Beulich wrote:
On 15.12.16 at 17:46, wrote:
>> On Thu, Dec 15, 2016 at 05:12:04PM +0100, Juergen Gross wrote:
>>> with today's kernel the system isn't coming up when booted as Xen dom0:
>> Remind me again pls, is dom0 even supposed to load microcode? Isn't the
>> hyperv
On Thu, Dec 15, 2016 at 12:42 AM, Peter Zijlstra wrote:
> On Wed, Dec 14, 2016 at 11:26:49PM -0800, Stephane Eranian wrote:
>> On Wed, Dec 14, 2016 at 9:55 AM, Peter Zijlstra wrote:
>> >
>> > Just spotted this again, ping?
>> >
>> Ok, on what processor running what command, so I can try and repro
From: Borislav Petkov
s/prink/printk/
Signed-off-by: Borislav Petkov
Cc: Olof Johansson
Cc: Andrew Morton
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 7446097f72bd..cb66a4648840 100644
--- a/lib/Kconfig.
(Adding Greg KH)
On Thu, 2016-12-15 at 11:54 +, Måns Rullgård wrote:
> Joe Perches writes:
>
> > On Wed, 2016-12-14 at 18:13 +, Måns Rullgård wrote:
> > > Alexey Dobriyan writes:
> > > > I call for a tree wide moratorium on pure coding style changes.
> >
> > []
> > > I'd relax this sli
On Thu, 15 Dec 2016 21:56:41 +0800
Cao jin wrote:
> On 12/15/2016 06:16 AM, Alex Williamson wrote:
> > On Wed, 14 Dec 2016 18:24:23 +0800
> > Cao jin wrote:
> >
> >> Sorry for late.
> >> after reading all your comments, I think I will try the solution 1.
> >>
> >> On 12/13/2016 03:12 AM, Alex
v3:
* fixes off-by-one error in [2/4]
* moves phys_map changes from [2/4] to [4/4]; [2/4] doesn't carry
David's r-b to [v2 2/4] because of this change
* expands a comment in [4/4]
v2: http://www.spinics.net/lists/kvm/msg142414.html
> Removes the capability that let userspace know of chan
Interrupt to self can be sent without knowing the APIC ID.
Reviewed-by: David Hildenbrand
Signed-off-by: Radim Krčmář
---
v2: r-b David
---
arch/x86/kvm/hyperv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
index 99cde522
There were three calls sites:
- recalculate_apic_map and kvm_apic_match_physical_addr, where it would
only complicate implementation of x2APIC hotplug;
- in apic_debug, where it was still somewhat preserved, but keeping the
old function just for apic_debug was not worth it
Signed-off-by: R
Slow path tried to prevent IPIs from x2APIC VCPUs from being delivered
to xAPIC VCPUs and vice-versa. Make slow path behave like fast path,
which never distinguished that.
Signed-off-by: Radim Krčmář
---
arch/x86/kvm/lapic.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
On Thu, 15 Dec 2016 10:36:02 +0100
Auger Eric wrote:
> Hi,
>
> On 14/12/2016 20:39, Alex Williamson wrote:
> > This sample driver was originally under Documentation/ and was moved
> > to samples, but build support was never adjusted for the new location.
> >
> > Signed-off-by: Alex Williamson
LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of
VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI,
but there is no way to uniquely address it using xAPIC.
>From many possible options, we chose the one that also works on real
hardware: accepting interrupt
On Thu, 15 Dec 2016 15:17:46 +0530
Kirti Wankhede wrote:
> On 12/15/2016 1:42 PM, Alex Williamson wrote:
> > On Thu, 15 Dec 2016 13:15:34 +0530
> > Kirti Wankhede wrote:
> >
> >> On 12/15/2016 1:09 AM, Alex Williamson wrote:
> >>> This sample driver was originally under Documentation/ and w
On Thu, Dec 15, 2016 at 08:59:56AM -0800, Stephane Eranian wrote:
> On Thu, Dec 15, 2016 at 12:42 AM, Peter Zijlstra wrote:
> > On Wed, Dec 14, 2016 at 11:26:49PM -0800, Stephane Eranian wrote:
> >> On Wed, Dec 14, 2016 at 9:55 AM, Peter Zijlstra
> >> wrote:
> >> >
> >> > Just spotted this again
On Thu, Dec 15, 2016 at 03:34:43PM +0100, Petr Mladek wrote:
> We have to find the right balance. For example, we do not show
> messages immediately in NMI context because there is a risk
> of a deadlock.
I find the occasional deadlock much preferable to guaranteed no output.
On Thu, Dec 15, 2016 at 11:54:54AM +, Måns Rullgård wrote:
> Joe Perches writes:
>
> > On Wed, 2016-12-14 at 18:13 +, Måns Rullgård wrote:
> >> Alexey Dobriyan writes:
> >> > I call for a tree wide moratorium on pure coding style changes.
> > []
> >> I'd relax this slightly and say don't
tpm/st33zp24/st33zp24.c does not use any miscdevice so this patch remove
this unnecessary inclusion.
Signed-off-by: Corentin Labbe
---
drivers/char/tpm/st33zp24/st33zp24.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/char/tpm/st33zp24/st33zp24.c
b/drivers/char/tpm/st33zp24/st33zp2
On Thu, Dec 15, 2016 at 04:22:53PM +0800, Gaosheng Wu wrote:
> From: GaoShengWu
>
> Line 28 of kthread.c violates chapter 3 of CodingStyle - put the opening
> brace last on the line, and put the closing brace first.
>
> Signed-off-by: GaoShengWu
Please do coding style fixes on drivers/staging/
Hi Linus,
This time there are a few patches from the driver-core tree in this
pull-request, which you already pulled from Greg. The reason is that I
had to merge the driver-core-next branch to get the device dependency
link patches into my tree, because the changes for the Exynos IOMMU
driver in t
301 - 400 of 753 matches
Mail list logo
