On Thu, 27 Oct 2016 02:59:16 +0530
Kirti Wankhede wrote:
> VFIO IOMMU drivers are designed for the devices which are IOMMU capable.
> Mediated device only uses IOMMU APIs, the underlying hardware can be
> managed by an IOMMU domain.
>
> Aim of this change is:
> - To use most of the code of TYPE1
On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
wrote:
>
> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
> does seem to disable a lot of build-time testing.
Actually, we should probably just make the MEMORY_HOTPLUG dependency be
depends on COMPILE_TEST || !KASAN
s
On Thu, 27 Oct 2016, Ye Xiaolong wrote:
> Yes, this is weird, the per_thread_ops change is small and should be run
> to run variation, the actual significant change is
> will-it-scale.time.user_time
> -27% decrease, but the patch seems not relevant, we can't interpret it. :(
>
> We've tried to qu
Linus Torvalds writes:
> On Tue, Oct 25, 2016 at 4:46 PM, Rusty Russell wrote:
>>
>> Rusty Russell (1):
>> MAINTAINERS: Begin module maintainer transition
>
> Jessica, do you have a pgp key? And Rusty, have you signed it? That
> makes the whole "pull signed tags" transition nicer..
Well, I
On Thu, Oct 27, 2016 at 4:01 PM, Linus Torvalds
wrote:
> On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
> wrote:
>>
>> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
>> does seem to disable a lot of build-time testing.
>
> Actually, we should probably just make the MEMORY_H
On Thu, Oct 27, 2016 at 03:25:43PM -0700, Deepa Dinamani wrote:
> >> struct timeval is not y2038 safe.
> >> All usage of timeval in the kernel will be replaced by
> >> y2038 safe structures.
> >>
> >> struct input_event maintains time for each input event.
> >> Real time timestamps are not ideal fo
On 10/27/2016 03:32 PM, James Morris wrote:
> On Wed, 26 Oct 2016, Casey Schaufler wrote:
>
>> Create interfaces that make it possible to deal with process
>> attributes in the face of multiple "major" security modules.
>
> We don't have support for multiple major modules currently (perhaps ever)
On 27/10/2016 at 20:02:29 +0200, Uwe Kleine-König wrote :
> Hello Richard,
>
> On Thu, Oct 27, 2016 at 06:04:06PM +0200, Richard Genoud wrote:
> > diff --git a/drivers/tty/serial/atmel_serial.c
> > b/drivers/tty/serial/atmel_serial.c
> > index fd8aa1f4ba78..168b10cad47b 100644
> > --- a/drivers/t
On Wed, Oct 19, 2016 at 11:28 AM, Mark Rutland wrote:
> When CONFIG_THREAD_INFO_IN_TASK is selected, the current_thread_info()
> macro relies on current having been defined prior to its use. However,
> not all users of current_thread_info() include , and thus
> current is not guaranteed to be defi
On 10/27/2016 01:40 PM, Arnaldo Carvalho de Melo wrote:
From: Namhyung Kim
Joonwoo reported that there's a mismatch between timestamps in script
and sched commands. This was because of difference in printing the
timestamp. Factor out the code and share it so that they can be in
sync. Also
ioremaped addresses are not linearly mapped so the physical
address can not be figured out via __pa. More generally, there
is no guarantee that backing value of an ioremapped address
is a physical address at all. The value here is only used
for debugging so just drop the call to __pa on the iorema
On Tue, Oct 25, 2016 at 8:52 AM, Arnd Bergmann wrote:
> A bugfix just tried to address a randconfig build problem and introduced
> a variant of the same problem: with CONFIG_LIBNVDIMM=y and
> CONFIG_NVDIMM_DAX=m, the nvdimm module now fails to link:
>
> drivers/nvdimm/built-in.o: In function `to_n
>From what I can tell by looking at the android 3.10 kernel
sources for msm8974, this isn't actually a reserved region.
Instead it's marked as "unused" for reserved regions. Let's
remove it so we get back a good chunk of memory.
Cc: Bjorn Andersson
Signed-off-by: Stephen Boyd
---
arch/arm/boot/
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: e3300ffef0653774f1099cab153d25d24bd773ce
commit: f47b72a15a9679dd4dc1af681d4d2f1ca2815552 PM / OPP: Move CONFIG_OF
dependent code in a separate file
date: 6 months ago
config: xtensa-allmodconfig (attached
On 10/27/2016 04:21 PM, Laura Abbott wrote:
ioremaped addresses are not linearly mapped so the physical
address can not be figured out via __pa. More generally, there
is no guarantee that backing value of an ioremapped address
is a physical address at all. The value here is only used
for debuggin
On Thu, Oct 27, 2016 at 4:05 PM, Alexander Potapenko wrote:
>
> Maybe we could just reverse the MEMORY_HOTPLUG->!KASAN dependency to
> make it KASAN->!MEMORY_HOTPLUG?
Yes, that was my initial approach too, but then I decided that I'd
rather build-test both together anyway. Since I can. So that ju
On Thu, Oct 27, 2016 at 4:00 PM, Rusty Russell wrote:
>
> Well, I don't know her, I just know her work.
>
> But I'll figure it out. I see a module implementation trivia game in my
> future!
It's fine, and I certainly don't require any key signing on
maintainership change, it's just obviously a n
Hi Jon,
I noticed that you left some conflict markers in
Documentation/admin-guide/index.rst in merge commit
7a6992dc952e ("Merge branch 'doc-tweaks' into docs-next")
--
Cheers,
Stephen Rothwell
On Wed, October 26, 2016 11:00 am, Dmitry Torokhov wrote:
>
> Yeah, if device happens to be plugged at boot time it will wait that
> long before even getting to mount rootfs if driver is built into the
> kernel.
Not a case I had considered... that would probably be bad. I'll look at
coding up a wo
On 10/27, Laura Abbott wrote:
> On 10/27/2016 04:21 PM, Laura Abbott wrote:
> >
> >@@ -269,7 +267,7 @@ static int xgene_clk_enable(struct clk_hw *hw)
> > xgene_clk_write(data, pclk->param.csr_reg +
> > pclk->param.reg_csr_offset);
> > pr_d
So, would you be OK with the following patch ?
There is a symmetry just like irq_vectors tracepoints:
# perf list | grep -E "exception|irq_vectors"
exceptions:page_fault_kernel_entry [Tracepoint event]
exceptions:page_fault_kernel_exit [Tracepoint event]
ex
The tracepoints "exceptions:page_fault_(user|kernel)" were renamed
"exceptions:page_fault_(user|kernel)_entry". Two more tracepoints were
added: "exceptions:page_fault_(user|kernel)_exit". These events are
called right before and after __do_page_fault().
Signed-off-by: Alexis Berlemont
---
arch/
Hi Linus,
On Thu, 27 Oct 2016 16:01:22 -0700 Linus Torvalds
wrote:
>
> In the meantime, thanks for noticing and letting me know.
It was pointed out by the extra checking you asked me to add in order
to easier detect new warnings for code added to linux-next :-)
--
Cheers,
Stephen Rothwell
Hi Gregoire,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on next-20161027]
[cannot apply to v4.9-rc2]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --b
On Thu, Oct 27, 2016 at 03:02:30PM -0700, Brian Norris wrote:
> In reading through a USB interface driver, I noticed that it called
> usb_{get,put}_dev() in its probe() and disconnect() methods. This seemed
> unnecessary, but a look at the comments here matched the usage.
>
> USB interface devices
On Fri, 28 Oct 2016 10:30:29 +1100
Stephen Rothwell wrote:
> I noticed that you left some conflict markers in
> Documentation/admin-guide/index.rst in merge commit
>
> 7a6992dc952e ("Merge branch 'doc-tweaks' into docs-next")
Argh. I noticed that too, but failed to amend the merge before pus
On Thu, Oct 27, 2016 at 03:32:10PM -0400, Joe Korty wrote:
> Hi Al,
> I don't know if this is worth fixing or not, but I thought
> I would mention it in case it was.
>
> A git bisect search shows that the commit:
>
> commit 319fe11519401e8a5db191a0a93aa2c1d7bb59f4
> Author: Al Viro
> Date:
On 10/27/2016 3:32 PM, James Morris wrote:
> On Wed, 26 Oct 2016, Casey Schaufler wrote:
>
>> Create interfaces that make it possible to deal with process
>> attributes in the face of multiple "major" security modules.
> We don't have support for multiple major modules currently (perhaps ever),
>
On Thu, Sep 22, 2016 at 3:15 PM, Andy Lutomirski wrote:
> On Thu, Sep 22, 2016 at 2:33 PM, J Freyensee
> wrote:
>> On Thu, 2016-09-22 at 14:43 -0600, Jens Axboe wrote:
>>> On 09/22/2016 02:11 PM, Andy Lutomirski wrote:
>>> >
>>> > On Thu, Sep 22, 2016 at 7:23 AM, Jens Axboe wrote:
>>> > >
>>> >
On Thu, 2016-10-27 at 12:42 -0500, Franklin S Cooper Jr wrote:
>
> On 10/27/2016 05:34 AM, Bastien Nocera wrote:
> > On Wed, 2016-10-26 at 18:18 -0500, Rob Herring wrote:
> > > On Thu, Oct 20, 2016 at 02:59:17PM -0500, Franklin S Cooper Jr
> > > wrote:
> > > >
> >
> >
> > > I'm not sure I follo
x86 has an option CONFIG_DEBUG_VIRTUAL to do additional checks
on virt_to_phys calls. The goal is to catch users who are calling
virt_to_phys on non-linear addresses immediately. As features
such as CONFIG_VMAP_STACK get enabled for arm64, this becomes
increasingly important. Add checks to catch ba
On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote:
> The "imply" keyword is a weak version of "select" where the target
> config symbol can still be turned off, avoiding those pitfalls that come
> with the "select" keyword.
>
> This is useful e.g. with multiple drivers that want to indicate t
We need to wait until the percpu_ref is released before exit. Otherwise,
we sometimes lose the race and trigger this new warning that was added
in v4.9 (commit a67823c1ed10 "percpu-refcount: init ->confirm_switch
member properly"):
WARNING: CPU: 0 PID: 3629 at lib/percpu-refcount.c:107
percpu_re
ATU (Address Translation Unit) is a new IOMMU in SPARC supported with
sun4v hypervisor PCI IOMMU v2 APIs.
Current SPARC IOMMU supports only 32bit address ranges and one TSB
per PCIe root complex that has a 2GB per root complex DVMA space
limit. The limit has become a scalability bottleneck nowaday
ATU 64bit addressing allows PCIe devices with 64bit DMA capabilities
to use ATU for 64bit DMA.
Signed-off-by: Tushar Dave
Reviewed-by: chris hyser
Acked-by: Sowmini Varadhan
---
arch/sparc/Kconfig| 4
arch/sparc/kernel/iommu.c | 8 ++--
2 files changed, 10 insertions(+), 2 del
Like legacy IOMMU, use common iommu_map_table and iommu_pool for ATU.
This change initializes iommu_map_table and iommu_pool for ATU.
Signed-off-by: Tushar Dave
Reviewed-by: chris hyser
Reviewed-by: Sowmini Varadhan
---
arch/sparc/include/asm/iommu_64.h | 2 ++
arch/sparc/kernel/pci_sun4v.c
From: Dave Kleikamp
This change allows ATU (new IOMMU) in SPARC systems to request
large (32M) contiguous memory during boot for creating IOTSB backing
store.
Signed-off-by: Dave Kleikamp
Signed-off-by: Tushar Dave
---
arch/sparc/Kconfig | 18 ++
1 file changed, 18 insertions(
UFS devfreq clock scaling work may require clocks to be ON if it need to
execute some UFS commands hence it may request for clock hold before
issuing the command. But if UFS clock gating work is already running in
parallel, ungate work would end up waiting for the clock gating work to
finish and as
On 10/27, Rob Herring wrote:
> On Fri, Oct 21, 2016 at 09:37:10AM +0800, Jiancheng Xue wrote:
> > Add CRG driver for Hi3798CV200 SoC. CRG(Clock and Reset
> > Generator) module generates clock and reset signals used
> > by other module blocks on SoC.
> >
> > Signed-off-by: Jiancheng Xue
> > ---
>
Add Hypervisor IOMMU v2 APIs pci_iotsb_map(), pci_iotsb_demap() and
enable sun4v dma ops to use IOMMU v2 API for all PCIe devices with
64bit DMA mask.
Signed-off-by: Tushar Dave
Reviewed-by: chris hyser
Acked-by: Sowmini Varadhan
---
arch/sparc/include/asm/hypervisor.h | 6 +
arch/sparc/kern
ATU (Address Translation Unit) is a new IOMMU in SPARC supported with
Hypervisor IOMMU v2 APIs.
Current SPARC IOMMU supports only 32bit address ranges and one TSB
per PCIe root complex that has a 2GB per root complex DVMA space
limit. The limit has become a scalability bottleneck nowadays that
a t
In order to use Hypervisor (HV) IOMMU v2 API for map/demap, each PCIe
device has to be bound to IOTSB using HV API pci_iotsb_bind().
Signed-off-by: Tushar Dave
Reviewed-by: chris hyser
Acked-by: Sowmini Varadhan
---
arch/sparc/kernel/pci_sun4v.c | 43 +++
If ufshcd pltfrm/pci driver's probe fails for some reason then ensure that
scsi host is released to avoid memory leak but managed memory allocations
(via devm_* calls) need not to be freed explicitly on probe failure as
memory allocated with these functions is automatically freed on driver
detach.
When we are resuming the UFS device rails in HPM mode, we are first
powering on the VCC rail while VCCQ and VCCQ2 rails still being in LPM
mode. Some UFS devices may take VCC on event as hint that host wants
UFS device to be resumed and may start drawing more power from the
VCCQ/VCCQ2 rails (while
Currently clock scaling is suspended only after the host and device
are put in low power mode but we should avoid clock scaling running
after UFS link is put in low power mode (hibern8). This change
suspends clock scaling before putting host/device in low power mode.
Reviewed-by: Sahitya Tummala
Hi Laura,
[auto build test WARNING on clk/clk-next]
[also build test WARNING on v4.9-rc2 next-20161027]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience) to rec
Hi-
I think this error on my laptop is new on 4.9 kernels:
[ +0.014696] tpm_tis 00:09: 1.2 TPM (device-id 0xFE, rev-id 2)
[ +0.012228] tpm tpm0: TPM self test failed
[ +0.19] tpm_tis: probe of 00:09 failed with error -14
Is this known?
At the very least, shouldn't the error message inclu
On 26 October 2016 at 16:53, Dave Airlie wrote:
> Hi Linus,
>
> This is a standalone pull request for the fix for a regression introduced
> in -rc1 by a change to vm_insert_mixed to start using the PAT range tracking
> to validate page protections. With this fix in place, all the VRAM mappings
> f
On Thu, 2016-10-27 at 17:23 -0700, Tushar Dave wrote:
> Add Hypervisor IOMMU v2 APIs pci_iotsb_map(), pci_iotsb_demap() and
> enable sun4v dma ops to use IOMMU v2 API for all PCIe devices with
> 64bit DMA mask.
trivia:
> diff --git a/arch/sparc/kernel/pci_sun4v.c b/arch/sparc/kernel/pci_sun4v.c
[
>From: Arnd Bergmann [mailto:a...@arndb.de]
>On Tuesday, October 25, 2016 4:26:28 PM CEST Sriram Dash wrote:
>> Do not use dma_coerce_mask_and_coherent for hcd.
>>
>> Signed-off-by: Arnd Bergmann
>
>The patch is good, but please follow the usual rules for submitting someone
>else's
>patch:
>
>- A
da7219 output (for headset capture) should be set to high-impedance when
not in use, since it will otherwise interfere with output from other
codecs attached to the same DAI.
Signed-off-by: Stephen Barber
---
sound/soc/codecs/da7219.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
On 10/21, Erin Lo wrote:
> diff --git a/drivers/clk/mediatek/clk-mt2701-bdp.c
> b/drivers/clk/mediatek/clk-mt2701-bdp.c
> new file mode 100644
> index 000..dbf6ab2
> --- /dev/null
> +++ b/drivers/clk/mediatek/clk-mt2701-bdp.c
> @@ -0,0 +1,148 @@
> +
> +static int mtk_bdpsys_init(struct platfor
在 2016/10/28 8:25, Stephen Boyd 写道:
> On 10/27, Rob Herring wrote:
>> On Fri, Oct 21, 2016 at 09:37:10AM +0800, Jiancheng Xue wrote:
>>> Add CRG driver for Hi3798CV200 SoC. CRG(Clock and Reset
>>> Generator) module generates clock and reset signals used
>>> by other module blocks on SoC.
>>>
>>>
From: Kuninori Morimoto
Current dw-hdmi is supporting sound via AHB bus, but it has
I2S audio feature too. This patch adds I2S audio support to dw-hdmi.
This HDMI I2S is supported by using ALSA SoC common HDMI encoder
driver.
Signed-off-by: Kuninori Morimoto
---
drivers/gpu/drm/bridge/Kconfig
The mm-of-the-moment snapshot 2016-10-27-18-27 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On 10/21, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez
>
> This patch introduces the support of the LSI & LSE clocks.
> The clock drivers needs to disable the power domain write protection
> using syscon/regmap to enable these clocks.
>
> Signed-off-by: Gabriel Fernandez
> ---
App
On 10/21, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez
>
> This patch introduces the support of the RTC clock.
> RTC clock can have 3 sources: lsi, lse and hse_rtc.
>
> Signed-off-by: Gabriel Fernandez
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of
On 10/21, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez
>
> This patch adds the QSPI clock for stm32f469 discovery board.
> The gate mapping is a little bit different from stm32f429 soc.
>
> Signed-off-by: Gabriel Fernandez
> ---
Applied to clk-next + added Rob's ack from v2.
--
On 10/19, Georgi Djakov wrote:
> Add support for the PLL, which generates the higher range of CPU
> frequencies on MSM8916 platforms.
>
> Signed-off-by: Georgi Djakov
Please Cc dt reviewers.
> ---
> .../devicetree/bindings/clock/qcom,a53-pll.txt | 17
> drivers/clk/qcom/Kconfig
On 2016/10/27 1:00, David Daney wrote:
> On 10/26/2016 06:43 AM, Robert Richter wrote:
>> On 25.10.16 14:31:00, David Daney wrote:
>>> From: David Daney
>>>
>>> On arm64 NUMA kernels we can pass "numa=off" on the command line to
>>> disable NUMA. A side effect of this is that kmalloc_node() cal
On 10/19, Georgi Djakov wrote:
> Add a driver for the A53 Clock Controller. It is a hardware block that
> implements a combined mux and half integer divider functionality. It can
> choose between a fixed-rate clock or the dedicated A53 PLL. The source
> and the divider can be set both at the same t
Boaz Harrosh wrote on 2016-10-26:
> On 10/26/2016 06:50 PM, Brian Boylston wrote:
>> copy_from_iter_nocache() now uses nocache copies for all types of iovecs
>> on x86, so the flush in arch_copy_from_iter_pmem() is no longer needed.
>>
>> Cc: Ross Zwisler
>> Cc: Thomas Gleixner
>> Cc: Ingo Molna
On 10/19, Georgi Djakov wrote:
> diff --git a/drivers/clk/qcom/clk-regmap-mux-div.c
> b/drivers/clk/qcom/clk-regmap-mux-div.c
> new file mode 100644
> index ..ec87f496606a
> --- /dev/null
> +++ b/drivers/clk/qcom/clk-regmap-mux-div.c
> @@ -0,0 +1,254 @@
> +/*
> + * Copyright (c) 2015,
On Fri, Oct 28, 2016 at 01:03:55AM +0100, Al Viro wrote:
> On Thu, Oct 27, 2016 at 03:32:10PM -0400, Joe Korty wrote:
[oops in 4.1.35, bisected to 319fe1151940]
> > The following test program can be used to trigger the problem:
> >
> > /* gcc -m32 c.c -o c */
> > #define _GNU_SOURCE
> > #include
Thomas Gleixner wrote on 2016-10-26:
> On Wed, 26 Oct 2016, Brian Boylston wrote:
>> --- a/arch/x86/include/asm/string_32.h
>> +++ b/arch/x86/include/asm/string_32.h
>> @@ -196,6 +196,9 @@ static inline void *__memcpy3d(void *to, const void
>> *from, size_t len)
>
>> +#define __HAVE_ARCH_MEMCPY_N
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
wb-buf-throttle
commit b1fa1b67c176e41eeae2bfcc7df38117976cd92d ("block: hook up writeback
throttling")
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -m 320M
caused
gt; great, but better be sure and run the tests.
>>
>> Reviewed-by: Cyrill Gorcunov
>
> Eric, on which kernel the patch is on top of?
> It doesn't apply on linux-next for some reason.
>
> | Date: Thu Oct 27 14:21:59 2016 +1100
> |
> | Add linux-nex
Boaz Harrosh wrote on 2016-10-26:
> On 10/26/2016 06:50 PM, Brian Boylston wrote:
>> Introduce memcpy_nocache() as a memcpy() that avoids the processor cache
>> if possible. Without arch-specific support, this defaults to just
>> memcpy(). For now, include arch-specific support for x86.
>>
>> Cc
On 27/10/16 23:31, Kirti Wankhede wrote:
>
>
> On 10/27/2016 12:50 PM, Alexey Kardashevskiy wrote:
>> On 18/10/16 08:22, Kirti Wankhede wrote:
>>> VFIO IOMMU drivers are designed for the devices which are IOMMU capable.
>>> Mediated device only uses IOMMU APIs, the underlying hardware can be
>>>
On 2016/10/11 5:53, Rob Herring wrote:
> On Mon, Oct 10, 2016 at 07:05:16PM +0800, Jian Yuan wrote:
>> From: yuanjian
>>
>> Add PWM driver for the PWM controller found on HiSilicon BVT SOCs, like
>> Hi3519V100, Hi3516CV300, etc.
>> The PWM controller is primarily in charge of controlling P-Iris
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of David Singleton
> Sent: Monday, October 17, 2016 9:51 AM
> To: Kirsher, Jeffrey T
> Cc: khalidm ; intel-wired-...@lists.osuosl.org;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [PATCH] e
On 10/26/2016 05:58 AM, Alexandre Bailon wrote:
When the phy is forced in host mode, only the first hot plug and
hot remove works. That is actually because the driver execute the
OTG workaround, whereas it is not applicable in host or device mode.
Indeed, to work correctly, the VBUS sense and ses
On 2016/10/21 15:34, Thierry Reding wrote:
> On Fri, Oct 21, 2016 at 09:22:36AM +0200, Thierry Reding wrote:
>> On Mon, Oct 10, 2016 at 04:53:39PM -0500, Rob Herring wrote:
>>> On Mon, Oct 10, 2016 at 07:05:16PM +0800, Jian Yuan wrote:
From: yuanjian
Add PWM driver for the PWM con
On Thu, Oct 27, 2016 at 05:33:57PM -0700, Andy Lutomirski wrote:
> Hi-
>
> I think this error on my laptop is new on 4.9 kernels:
>
> [ +0.014696] tpm_tis 00:09: 1.2 TPM (device-id 0xFE, rev-id 2)
> [ +0.012228] tpm tpm0: TPM self test failed
> [ +0.19] tpm_tis: probe of 00:09 failed with
On Fri, 28 Oct 2016, Paul Bolle wrote:
> On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote:
> > The "imply" keyword is a weak version of "select" where the target
> > config symbol can still be turned off, avoiding those pitfalls that come
> > with the "select" keyword.
> >
> > This is usefu
Radim Krčmář writes:
> 2016-10-26 20:17-0400, Bandan Das:
>> Radim Krčmář writes:
>> ...
>>> +static int check_fxsr(struct x86_emulate_ctxt *ctxt)
>>> +{
>>> + u32 eax = 1, ebx, ecx = 0, edx;
>>> +
>>> + ctxt->ops->get_cpuid(ctxt, &eax, &ebx, &ecx, &edx);
>>> + if (!(edx & FFL(FXSR)))
>>>
On Thu, Oct 27, 2016 at 8:49 AM, Sergey Senozhatsky
wrote:
>
> RFC
>
> This patch set extends a lock-less NMI per-cpu buffers idea to
> handle recursive printk() calls. The basic mechanism is pretty much the
> same -- at the beginning of a deadlock-prone section we switch to lock-l
Hi all,
There will probably be no linux-next releases next week while I attend
the Kernel Summit.
Changes since 20161027:
The akpm-current tree lost its build failures.
Non-merge commits (relative to Linus' tree): 3098
3842 files changed, 227213 insertions(+), 59787 dele
Add maintainer entry for Freescale SoC drivers including
the QE library and the GUTS driver now. Also add maintainer
for QE library.
Signed-off-by: Yangbo Lu
Acked-by: Scott Wood
Acked-by: Qiang Zhao
---
Changes for v8:
- Added this patch
Changes for v9:
- Added linux-arm mail l
On 28-10-16, 07:22, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: e3300ffef0653774f1099cab153d25d24bd773ce
> commit: f47b72a15a9679dd4dc1af681d4d2f1ca2815552 PM / OPP: Move CONFIG_OF
> dependent code in a separate file
> d
Add the dts node for device configuration unit that provides
general purpose configuration and status for the device.
Signed-off-by: Yangbo Lu
Acked-by: Scott Wood
---
Changes for v5:
- Added this patch
Changes for v6:
- None
Changes for v7:
- None
Changes for v8:
On 10/22/2016 05:47 AM, Robert Nelson wrote:
+#include
^ this hasn't been posted nor pushed to mainline yet.. ;)
Oops! I've created this file but not captured not only in my git tree
but also in my head! Thanks for your review.
Best regards,
Milo
This patchset is used to fix a host version register bug in the T4240-R1.0-R2.0
eSDHC controller. To match the SoC version and revision, 10 previous version
patchsets had tried many methods but all of them were rejected by reviewers.
Such as
- dts compatible method
- syscon method
The global utilities block controls power management, I/O device
enabling, power-onreset(POR) configuration monitoring, alternate
function selection for multiplexed signals,and clock control.
This patch adds a driver to manage and access global utilities block.
Initially only reading SVR and regis
Update Freescale DCFG compatible with 'fsl,-dcfg' instead
of 'fsl,ls1021a-dcfg' to include more chips such as ls1021a,
ls1043a, and ls2080a.
Signed-off-by: Yangbo Lu
Acked-by: Rob Herring
Signed-off-by: Scott Wood
---
Changes for v8:
- Added this patch
Changes for v9:
- Added a
On 10/26/2016 10:56 PM, Lee Jones wrote:
diff --git a/include/linux/mfd/tps65217.h b/include/linux/mfd/tps65217.h
> index 4ccda89..75a3a5f 100644
> --- a/include/linux/mfd/tps65217.h
> +++ b/include/linux/mfd/tps65217.h
> @@ -235,9 +235,9 @@ struct tps65217_bl_pdata {
> };
>
> enum tps65217_irq
Hello,
On (10/27/16 20:30), Linus Torvalds wrote:
> On Thu, Oct 27, 2016 at 8:49 AM, Sergey Senozhatsky
> wrote:
> >
> > RFC
> >
> > This patch set extends a lock-less NMI per-cpu buffers idea to
> > handle recursive printk() calls. The basic mechanism is pretty much the
> > same
On Fri, Oct 28, 2016 at 09:27:53AM +0530, Viresh Kumar wrote:
On 28-10-16, 07:22, kbuild test robot wrote:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: e3300ffef0653774f1099cab153d25d24bd773ce
commit: f47b72a15a9679dd4dc1af681d4d2f1ca2815552 PM / OPP
On (10/27/16 09:35), Joe Perches wrote:
[..]
> > - printk_nmi_flush_line(buf, (end - start) + 1);
> > + /* Handle continuous lines or missing new line. */
> > + if ((c + 1 < end) && printk_get_level(c)) {
> > + if (header) {
> > + c
Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/
since it's used by not only PowerPC but also ARM. And add a specification
for 'little-endian' property.
Signed-off-by: Yangbo Lu
Acked-by: Rob Herring
Acked-by: Scott Wood
---
Changes for v4:
- Added this patch
Chang
From: Arnd Bergmann
We keep running into cases where device drivers want to know the exact
version of the a SoC they are currently running on. In the past, this has
usually been done through a vendor specific API that can be called by a
driver, or by directly accessing some kind of version regist
This patch support to fix lock holder preemption issue.
For kernel users, we could use bool vcpu_is_preempted(int cpu) to detech if
one vcpu is preempted or not.
The default implementation is a macro defined by false. So compiler can
wrap it out if arch dose not support such vcpu pteempted check.
change from v5:
spilt x86/kvm patch into guest/host part.
introduce kvm_write_guest_offset_cached.
fix some typos.
rebase patch onto 4.9.2
change from v4:
spilt x86 kvm vcpu preempted check into two patches.
add documentation patch.
add x86 vc
An over-committed guest with more vCPUs than pCPUs has a heavy overload in
osq_lock().
This is because vCPU A hold the osq lock and yield out, vCPU B wait per_cpu
node->locked to be set. IOW, vCPU B wait vCPU A to run and unlock the osq
lock.
Kernel has an interface bool vcpu_is_preempted(int cpu
Support the vcpu_is_preempted() functionality under KVM. This will
enhance lock performance on overcommitted hosts (more runnable vcpus
than physical cpus in the system) as doing busy waits for preempted
vcpus will hurt system performance far worse than early yielding.
struct kvm_steal_time::preem
From: Juergen Gross
Support the vcpu_is_preempted() functionality under Xen. This will
enhance lock performance on overcommitted hosts (more runnable vcpus
than physical cpus in the system) as doing busy waits for preempted
vcpus will hurt system performance far worse than early yielding.
A quic
Support the vcpu_is_preempted() functionality under KVM. This will
enhance lock performance on overcommitted hosts (more runnable vcpus
than physical cpus in the system) as doing busy waits for preempted
vcpus will hurt system performance far worse than early yielding.
Use one field of struct kvm_
This is to fix some lock holder preemption issues. Some other locks
implementation do a spin loop before acquiring the lock itself.
Currently kernel has an interface of bool vcpu_is_preempted(int cpu). It
takes the cpu as parameter and return true if the cpu is preempted. Then
kernel can break the
Commit ("x86, kvm: support vcpu preempted check") add one field "__u8
preempted" into struct kvm_steal_time. This field tells if one vcpu is
running or not.
It is zero if 1) some old KVM deos not support this filed. 2) the vcpu is
not preempted. Other values means the vcpu has been preempted.
Sig
This is to fix some lock holder preemption issues. Some other locks
implementation do a spin loop before acquiring the lock itself.
Currently kernel has an interface of bool vcpu_is_preempted(int cpu). It
takes the cpu as parameter and return true if the cpu is preempted.
Then kernel can break the
701 - 800 of 847 matches
Mail list logo
