From: "Du, Changbin"
To stop an out endpoint, software should set sets the Global OUT NAK,
but not the Global Non-periodic IN NAK. This driver bug leads the out-ep
failed be in disabled state with below error.
dwc2_hsotg_ep_stop_xfr: timeout DOEPCTL.EPDisable
Signed-off-by: Du, Changbin
---
d
Hello
Change since v3
- rework the test logic with ver/err
Change since v2
- Invert a test logic
Change since v1
- Always return error code from kstrtox.
LABBE Corentin (1):
atm: solos-pci: Replace simple_strtol by kstrtoint
drivers/atm/solos-pci.c | 28 +---
1 file
The simple_strtol function is obsolete.
This patch replace it by kstrtoint.
This will simplify code, since some error case not handled by
simple_strtol are handled by kstrtoint.
Signed-off-by: LABBE Corentin
---
drivers/atm/solos-pci.c | 28 +---
1 file changed, 17 insert
* Borislav Petkov wrote:
> 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.
So when a hypervisor starts supporting RAPL we'll disable the driver
erroneously?
Isn't there any better method to detect
Hi,
On Fri, Dec 4, 2015 at 12:05 AM, Stefan Sperling wrote:
> Hi Emmanuel,
>
> As part of implementing 802.11n support in OpenBSD I'm looking for
> an AP which sends A-MSDUs. Preferrably under software control rather
> than firmware.
>
> I found your iwlwifi A-MSDU patches at
> http://marc.info/?
* Steven Rostedt wrote:
> On Fri, 04 Dec 2015 12:05:12 +1030
> Rusty Russell wrote:
>
> > This is clever, but I would advise against such subtle code. We will never
> > be
> > able to remove this code once it is in.
> >
> > Would suggest making the non-CPUMASK_OFFSTACK stubs write garbage
Ismail Kizir wrote:
> What means "did not look random"?
A plaintext consisting of repeated bytes (zero, or other values)
eventually makes your algorithm go into a loop, which results in
repeated bytes.
> On the pictures, there is also an example of "full 0"(it appears red,
> but it is full 0 bmp)
There is no need to worry about module and __init text disappearing
case, because that ftrace has a module notifier that is called when
a module is being unloaded and before the text goes away and this
code grabs the ftrace_lock mutex and removes the module functions
from the ftrace list, such that
From: "Du, Changbin"
When usb_ep_enable on a enabled ep, the configuration of the ep probably
has changed. In this scenario, the ep configuration in hw should be
reprogrammed by udc driver. Hence, it is better to return an error to
inform the caller.
Signed-off-by: Du, Changbin
---
include/lin
There is no need to worry about module and __init text disappearing
case, because that ftrace has a module notifier that is called when
a module is being unloaded and before the text goes away and this
code grabs the ftrace_lock mutex and removes the module functions
from the ftrace list, such that
There is no need to worry about module and __init text disappearing
case, because that ftrace has a module notifier that is called when
a module is being unloaded and before the text goes away and this
code grabs the ftrace_lock mutex and removes the module functions
from the ftrace list, such that
From: "Du, Changbin"
Queue a request to disabled ep doesn't make sense, and induce caller
make mistakes.
Here is a example for the android mtp gadget function driver. A mem
corruption can happen on below senario.
1) On disconnect, mtp driver disable its EPs,
2) During send_file_work and receive
There is no need to worry about module and __init text disappearing
case, because that ftrace has a module notifier that is called when
a module is being unloaded and before the text goes away and this
code grabs the ftrace_lock mutex and removes the module functions
from the ftrace list, such that
Fix the following similar misleading comments of ftrace for arch
ia64/metag/powerpc/sh/x86:
Note: Due to modules and __init, code can
disappear and change, we need to protect against faulting
as well as code changing. We do this by using the
probe_kernel_* functions.
No real locking needed, th
There is no need to worry about module and __init text disappearing
case, because that ftrace has a module notifier that is called when
a module is being unloaded and before the text goes away and this
code grabs the ftrace_lock mutex and removes the module functions
from the ftrace list, such that
On Fri, Dec 4, 2015 at 7:48 AM, Heiko Schocher wrote:
> Hello Frans,
>
> I just tried current mainline kernel:
> commit 2255702db4014d1c69d6037ed7bdad2d2e271985
> Merge: 9e5d25e c86576e
> Author: Linus Torvalds
> Date: Mon Nov 30 16:06:44 2015 -0800
>
> Merge tag 'mn10300-for-linus-v4.4-rc4
Hi,
On 04-12-15 00:56, Dmitry Torokhov wrote:
When Cypress protocol support is disabled cypress_init() is a stub that
always returns -ENOSYS, so there is not point in testing for
CONFIG_MOUSE_PS2_CYPRESS after we decided that we are dealing with a
Cypress device. Also, we should only be calling
Hi Manish
> > +static int rcar_thermal_of_get_temp(void *data, int *temp)
> > +{
> > + struct rcar_thermal_priv *priv = data;
> > +
> > + *temp = rcar_thermal_get_current_temp(priv);
> > +
> > + return 0;
> > +}
> > +
> > +static int rcar_thermal_get_temp(struct thermal_zone_dev
Hello Frans,
I just tried current mainline kernel:
commit 2255702db4014d1c69d6037ed7bdad2d2e271985
Merge: 9e5d25e c86576e
Author: Linus Torvalds
Date: Mon Nov 30 16:06:44 2015 -0800
Merge tag 'mn10300-for-linus-v4.4-rc4' of
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-stagi
I will also update the comment for the other arch that using the similar
description, such as ia64/metag/powerpc/sh/x86.
Thanks,
Li Bin
on 2015/12/4 10:50, Steven Rostedt wrote:
> On Fri, 4 Dec 2015 10:18:39 +0800
> Li Bin wrote:
>
>> There is no need to worry about module text disappearing case
Introduce a logging level for storvsc to log certain error/warning messages.
Those messages are helpful in some environments, e.g. Microsoft Azure, for
customer support and troubleshooting purposes.
Signed-off-by: Long Li
---
drivers/scsi/storvsc_drv.c | 34 +-
On Thu, Dec 03, 2015 at 09:10:44AM +0100, Vlastimil Babka wrote:
> Aaron, could you try this on your testcase?
One time result isn't stable enough, so I did 9 runs for each commit,
here is the result:
base: 25364a9e54fb8296837061bf684b76d20eec01fb
head: 7433b1009ff5a02e1e9f3444802daba2cf385d27
(h
On 2015/12/01, 15:05, "Valdis Kletnieks" wrote:
>Start of a batch series to clean up the Lustre tree. Other people have
>done some sparse and checkpatch cleanups, but I found a bunch of
>stuff building with W=1.
Hello Valdis,
thanks for these patches. Strictly speaking, they should also be sen
Hi
> +static int rcar_thermal_of_get_temp(void *data, int *temp)
> +{
> + struct rcar_thermal_priv *priv = data;
> +
> + *temp = rcar_thermal_get_current_temp(priv);
> +
> + return 0;
> +}
> +
> +static int rcar_thermal_get_temp(struct thermal_zone_device *zone, int *temp)
> +{
cpufreq governors evaluate load at sampling rate and based on that they
update frequency for a group of CPUs belonging to the same cpufreq
policy.
This is required to be done in a single thread for all policy->cpus, but
because we don't want to wakeup idle CPUs to do just that, we use
deferrable w
On 04-12-15, 02:18, Rafael J. Wysocki wrote:
> > + shared->skip_work--;
>
> Is there any reason for incrementing and decrementing this instead of setting
> it to either 0 or 1 (or maybe either 'true' or 'false' for that matter)?
>
> If my reading of the patch is correct, it can only be either 0
Counter overflow detection use for overflow interrupt
Signed-off-by: Yoshinori Sato
---
drivers/clocksource/h8300_timer16.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/clocksource/h8300_timer16.c
b/drivers/clocksource/h8300_timer16.c
index fc14a3f.
Signed-off-by: Yoshinori Sato
---
drivers/clocksource/h8300_timer16.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/clocksource/h8300_timer16.c
b/drivers/clocksource/h8300_timer16.c
index b14a8da..934ed0b 100644
--- a/drivers/clocksource/h8300_timer16.c
+++ b/
Signed-off-by: Yoshinori Sato
---
drivers/clocksource/h8300_timer8.c | 40 ++
1 file changed, 6 insertions(+), 34 deletions(-)
diff --git a/drivers/clocksource/h8300_timer8.c
b/drivers/clocksource/h8300_timer8.c
index aa4b2a98..1ba453b 100644
--- a/drivers/cl
Signed-off-by: Yoshinori Sato
---
drivers/clocksource/h8300_timer16.c | 40 +
drivers/clocksource/h8300_timer8.c | 25 +--
drivers/clocksource/h8300_tpu.c | 22 ++--
3 files changed, 44 insertions(+), 43 deletions(-)
di
Signed-off-by: Yoshinori Sato
---
drivers/clocksource/h8300_timer8.c | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers/clocksource/h8300_timer8.c
b/drivers/clocksource/h8300_timer8.c
index 1ba453b..9087dd2 100644
--- a/drivers/clocksource/h8300_timer8.c
Hi Daniel, Thomas,
Update h8300 clocksource / clockevents driver
Changes bellow
h8300_timer8.c:
Cleanup set_next_event handler.
Use ioread / iowrite functions.
h8300_timer16.c:
Overflow handling fix.
Use ioread / iowrite functions.
h8300_tpu.c:
Use ioread / iowrite functions.
Thanks.
Yoshinor
Sometimes udevadm trigger --action=add hangs the system, and the splat
below happens. This seems to be timing dependent, and I haven't been
able to trigger it yet with lockdep enabled, sadly.
Any ideas? I not, I'll try to instrument it better tomorrow.
This is 4.4-rc3 plus some patches that I d
Hi Arnd,
2015-12-01 20:29 GMT+09:00 Arnd Bergmann :
> On Tuesday 01 December 2015 13:30:25 Masahiro Yamada wrote:
>> Hello experts,
>>
>> I am tackling on a new bus driver, but I am worndering
>> what the DT-binding specification should be.
>>
>> Here is my hardware situation:
>>
>> My SoC has a
The UniPhier System Bus is a simple external that connects on-board
devices to the UniPhier SoC. Each bank (chip select) is dynamically
mapped to the CPU-viewed address base via the bus controller. The
bus controller must be configured before any access to the bus.
This driver parses the "ranges
On Thu, Dec 03, 2015 at 04:47:29PM +0100, Michal Hocko wrote:
> On Thu 03-12-15 15:58:50, Michal Hocko wrote:
> []
> > Warning, this looks ugly as hell.
>
> I was thinking about it some more and it seems that we should rather not
> bother with partial thp at all and keep it in the original mem
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 privil
>
>>
>> =
>> spi: xilinx - minimize iomem reads
>>
>> If this IP core is accessed through bridges like PCI-e, reads are rather
>> costly. Doing many reads or read-modify-writes is thus long and strenuous
>> on the CPU (active waiting).
>>
>> The transfer workflow of this
On 3 December 2015 at 23:49, Mikulas Patocka wrote:
>
>
> On Thu, 3 Dec 2015, Baolin Wang wrote:
>
>> On 3 December 2015 at 10:56, Baolin Wang wrote:
>> > On 3 December 2015 at 03:56, Alasdair G Kergon wrote:
>> >> On Wed, Dec 02, 2015 at 08:46:54PM +0800, Baolin Wang wrote:
>> >>> These are the
On 3 December 2015 at 23:47, Mikulas Patocka wrote:
>
>
> On Thu, 3 Dec 2015, Baolin Wang wrote:
>
>> On 3 December 2015 at 03:56, Alasdair G Kergon wrote:
>> > On Wed, Dec 02, 2015 at 08:46:54PM +0800, Baolin Wang wrote:
>> >> These are the benchmarks for request based dm-crypt. Please check it.
From: Kan Liang
The uncore subsystem for Broadwell-EP is similar to Haswell-EP.
There are some differences in pci device IDs, box number and
constraints. This patch extends the Broadwell-DE codes to support
Broadwell-EP.
Signed-off-by: Kan Liang
---
arch/x86/kernel/cpu/perf_event_intel_uncore.
Hi Arnd,
On 2015/12/3 17:40, Arnd Bergmann wrote:
> On Thursday 03 December 2015 10:42:45 Jiancheng Xue wrote:
>> --- a/arch/arm/mach-hisi/Kconfig
>> +++ b/arch/arm/mach-hisi/Kconfig
>> @@ -12,6 +12,14 @@ if ARCH_HISI
>>
>> menu "Hisilicon platform type"
>>
>> +config ARCH_HI3519
>> + b
At some point after humans go extinct and robots cotrol the world, dividing
he time64_t by 86400 to extract the days will overflow a 32bit integer,
leading to incorrect conversion into rtc_time in rtc_time64_to_tm().
Signed-off-by: Sasha Levin
---
drivers/rtc/rtc-lib.c |7 +++
1 file cha
Add config option CONFIG_SERIAL_8250_AMD in use of AMD carrizo.
Because carrizo's UART DMA device is an amba device, it selects
ARM_AMBA option. Anything uses amba devices must select ARM_AMBA.
Signed-off-by: Wang Hongcheng
---
drivers/tty/serial/8250/Kconfig | 8
1 file changed, 8 ins
From: Wan Zongshun
AMD UART is a ACPI HID named device, it also is none-pci device,
currently, iommu driver only supports pci device, so UART DMA did
not work at current AMD IOMMU driver.
AMD reused 8250 serial driver and ARM PL330 DMA engine driver,
since AMD uart and dma ips are compatible wit
For ftrace on arm64, kstop_machine which is hugely disruptive
to a running system is not needed to convert nops to ftrace calls
or back, because that to be modified instrucions, that NOP, B or BL,
are all safe instructions which called "concurrent modification
and execution of instructions", that c
Because amd iommu and software iommu need this mask.For example,
if we use software iommu without this mask, we will
get 'Out of SW-IOMMU space' error, when calling swiotlb_map_page
function.
Signed-off-by: Wan Zongshun
Signed-off-by: Wang Hongcheng
---
drivers/dma/pl330.c | 4
1 file chan
AMD pl330 is a UART DMA device, it shares one ACPI item with UART. So
a platform device and an acpi device will be created according to
AMD0020 ACPI dev. And its mem base address must have an offset. As a
result, MULTI_ATTACHED_QUIRK and MULTI_ATTACHED_QUIRK are used.
Signed-off-by: Wang Hongcheng
has_no_cap_mask means this device has no preset cap mask.
mcbuf_sz means bytes to allocate for MC buffer.
flags is for irq sharing, default is non-shared, in AMD
Carrizo, pl330 shares IRQ with its corresponding UART device.
Signed-off-by: Wang Hongcheng
---
drivers/acpi/acpi_apd.c| 13 ++
v2:
Based on the comments from Will and Steve,
1. Modify the commit message
2. Fix the misleading comments for ftrace_modify_code
v3:
Modify the comments again based on the comment from Steve.
Link: https://lkml.org/lkml/2015/12/3/422
Li Bin (2):
arm64: ftrace: stop using kstop_machine to enab
Set a new port type for AMD Carrizo. Add has_pl330_dma to 8250_dw's
private data and init fcr,ier as well as dma rx size.
Signed-off-by: Wang Hongcheng
---
drivers/acpi/acpi_apd.c | 10 ++
drivers/tty/serial/8250/8250_dw.c | 16
drivers/tty/serial/8250/825
Hi all,
As AMD carrizo UART device is compatible with 8250 and has pl330 DMA
IP, our uart driver is serial:8250 and DMA engines are registered by
driver/dma/pl330. The following patches are made, in order to enable
DMA.
Firstly, we add an universal ACPI amba glue layer to create an amba
device ba
register acpi_dma controller, so ACPI devices can request pl330 DMA
channel.
A filter is added in private data for Carrizo specific hardware
design
Signed-off-by: Wang Hongcheng
---
drivers/acpi/acpi_apd.c| 12
drivers/dma/pl330.c| 38
From: Huang Rui
Inspired by acpi platform bus type, to make driver "porting" more
straightforward, this patch introduces ACPI support to the AMBA bus
type. Instead of writing ACPI "glue" drivers for the exiting AMBA
drivers.
In the subsequent patches, we will use this function to support pl330
A
There is no need to worry about module and __init text disappearing
case, because that ftrace has a module notifier that is called when
a module is being unloaded and before the text goes away and this
code grabs the ftrace_lock mutex and removes the module functions
from the ftrace list, such that
Hi Arnd,
On 2015/12/3 17:41, Arnd Bergmann wrote:
> On Thursday 03 December 2015 10:49:37 Jiancheng Xue wrote:
>> Rename ARCH_HI3xxx to ARCH_HI36xx.
>>
>> Signed-off-by: Jiancheng Xue
>
> Maybe just change it to 'depends on ARCH_HISI'? That would make it
> possible to merge the change independen
From: Wan Zongshun
Add ivrs_acpihid kernel parameter description,
like ivrs_acpihid[00:14.5]=AMD0020:0.
Signed-off-by: Wan Zongshun
---
Documentation/kernel-parameters.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/kernel-parameters.txt
b/Documentation/kernel-par
Hi Arnd,
On 2015/12/3 17:44, Arnd Bergmann wrote:
> On Thursday 03 December 2015 10:39:24 Jiancheng Xue wrote:
>> +#ifndef __DTS_HI3519_CLOCK_H
>> +#define __DTS_HI3519_CLOCK_H
>
> Please try to avoid adding headers like this if you can at all.
>
> I might ask you to merge the header file in one
on 2015/12/4 10:50, Steven Rostedt wrote:
> On Fri, 4 Dec 2015 10:18:39 +0800
> Li Bin wrote:
>
>> There is no need to worry about module text disappearing case,
>> because that ftrace has a module notifier that is called when
>> a module is being unloaded and before the text goes away, and this
From: Kuninori Morimoto
This patch enables to use thermal-zone on r8a7791.
This thermal sensor can measure temperature from -4 to 125000,
but over 117000 can be critical on this chip.
Thus, default critical temperature is now set as 115000 (this driver
is using 5000 steps) (Current critical
From: Kuninori Morimoto
This patch enables to use thermal-zone on r8a7790.
This thermal sensor can measure temperature from -4 to 125000,
but over 117000 can be critical on this chip.
Thus, default critical temperature is now set as 115000 (this driver
is using 5000 steps) (Current critical
From: Kuninori Morimoto
This patch enables to use thermal-zone on DT if it was call as
"renesas,rcar-thermal-gen2".
Previous style is still supported by "renesas,rcar-thermal".
Signed-off-by: Kuninori Morimoto
---
.../devicetree/bindings/thermal/rcar-thermal.txt | 37 +-
dri
From: Kuninori Morimoto
This patch is prepare for of-thermal support.
Signed-off-by: Kuninori Morimoto
---
drivers/thermal/rcar_thermal.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/thermal/rcar_thermal.c b/drivers/thermal/rcar_thermal.c
index 13d0
Hi
These are enable to use thermal-zone on r8a7790/r8a7791.
The rcar thermal driver can use of-thermal style zone by this patch,
but it still keeping current style too.
You can select trip temp by DT if you use of-thermal style (this patch).
If not, it will use fixed trip temp.
Kuninori Morimot
On Fri, 4 Dec 2015 10:18:38 +0800
Li Bin wrote:
> For ftrace on arm64, kstop_machine which is hugely disruptive
> to a running system is not needed to convert nops to ftrace calls
> or back, because that to be modified instrucions, that NOP, B or BL,
> are all safe instructions which called "conc
Make sure the tv_usec makes sense. We might multiply them later which can
cause an overflow and undefined behavior.
Signed-off-by: Sasha Levin
---
kernel/time/timekeeping.c |4
1 file changed, 4 insertions(+)
diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
index d563
ROL on a 32 bit integer with a shift of 32 or more is undefined and the
result is arch-dependent. Avoid this by handling the trivial case of
roling by 0 correctly.
The trivial solution of checking if shift is 0 breaks gcc's detection
of this code as a ROL instruction, which is unacceptable.
This
Thanks Joe.
I'll send out another patch.
> -Original Message-
> From: Joe Perches [mailto:j...@perches.com]
> Sent: Thursday, December 3, 2015 6:28 PM
> To: Long Li ; KY Srinivasan ;
> Haiyang Zhang ; James E.J. Bottomley
>
> Cc: de...@linuxdriverproject.org; linux-s...@vger.kernel.org;
On Tue, Dec 1, 2015 at 10:39 PM, Dmitry V. Krivenok
wrote:
> This simple change hides pfn_seed attribute for non pmem
> regions because they don't support pfn anyway.
>
> Signed-off-by: Dmitry V. Krivenok
> ---
Looks good I'll queue it for 4.5.
--
To unsubscribe from this list: send the line "un
On Tue, Dec 1, 2015 at 1:48 PM, Dmitry V. Krivenok
wrote:
> In order to bind namespace to the driver user must first
> set all mandatory attributes in the following order:
> - uuid
> - size
> - sector_size (for blk namespace only)
>
> If the order is wrong, then user either won't be able to set
>
On Fri, 4 Dec 2015 10:18:39 +0800
Li Bin wrote:
> There is no need to worry about module text disappearing case,
> because that ftrace has a module notifier that is called when
> a module is being unloaded and before the text goes away, and this
> code grabs the ftrace_lock mutex and removes the
when ip fail to enter sleep mode, register access protection will
be disabed, at the same time if all clocks are disabled, access
register will hang up AHB bus.
the common case causes ip sleep fail is that after all ports enter
U3 but before ip enters sleep mode, a port receives a resume
signal('K'
On Fri, 04 Dec 2015 12:05:12 +1030
Rusty Russell wrote:
> This is clever, but I would advise against such subtle code. We will
> never be able to remove this code once it is in.
>
> Would suggest making the non-CPUMASK_OFFSTACK stubs write garbage into
> the cpumasks instead, iff !(flags & __GF
Hi Arnd,
Thank you very much for all your comments.
On 2015/12/3 17:36, Arnd Bergmann wrote:
> On Thursday 03 December 2015 10:44:28 Jiancheng Xue wrote:
>
>> +
>> +/dts-v1/;
>> +#include "hi3519.dtsi"
>> +
>> +/ {
>> +model = "HiSilicon HI3519 DEMO Board";
>> +compatible = "hisilicon,
On Thu, 2015-12-03 at 19:47 -0800, Long Li wrote:
> Introduce a logging level for storvsc to log certain error/warning
> messages. Those messages are helpful in some environments, e.g.
> Microsoft Azure, for customer support and troubleshooting purposes.
[]
> diff --git a/drivers/scsi/storvsc_drv.c
On 03.12.2015 19:30, Ben Gamari wrote:
> Krzysztof Kozlowski writes:
>
>> On 03.12.2015 06:19, Ben Gamari wrote:
>>> From: Thomas Abraham
>>>
>>> With the addition of the new Samsung specific cpu-clock type, the
>>> arm clock can be represented as a cpu-clock type. Add the CPU clock
>>> configur
On 12/02/2015 08:36 PM, Michael S. Tsirkin wrote:
> On Wed, Dec 02, 2015 at 01:04:03PM +0800, Jason Wang wrote:
>>
>> On 12/01/2015 10:43 PM, Michael S. Tsirkin wrote:
>>> On Tue, Dec 01, 2015 at 01:17:49PM +0800, Jason Wang wrote:
On 11/30/2015 06:44 PM, Michael S. Tsirkin wrote:
> On W
v2:
Based on the comments from Will and Steve,
1. Modify the commit message
2. Fix the misleading comments for ftrace_modify_code
Link: https://lkml.org/lkml/2015/12/3/422
Li Bin (2):
arm64: ftrace: stop using kstop_machine to enable/disable tracing
arm64: ftrace: fix the comments for ftrace_
For ftrace on arm64, kstop_machine which is hugely disruptive
to a running system is not needed to convert nops to ftrace calls
or back, because that to be modified instrucions, that NOP, B or BL,
are all safe instructions which called "concurrent modification
and execution of instructions", that c
There is no need to worry about module text disappearing case,
because that ftrace has a module notifier that is called when
a module is being unloaded and before the text goes away, and this
code grabs the ftrace_lock mutex and removes the module functions
from the ftrace list, such that it will n
Introduce a logging level for storvsc to log certain error/warning messages.
Those messages are helpful in some environments, e.g. Microsoft Azure, for
customer support and troubleshooting purposes.
Signed-off-by: Long Li
---
drivers/scsi/storvsc_drv.c | 30 +-
1 fi
On 2015/12/3 23:11, Paolo Bonzini wrote:
In theory this should have broken EPT on 32-bit kernels (due to
reading the high part of natural-width field GUEST_CR3). Not sure
if no one noticed or the processor behaves differently from the
documentation.
It seems we will check the success of vmcs_w
calibrate HS slew rate and switch 100uA current to SSUSB
to improve HS eye diagram of HQA test.
Signed-off-by: Chunfeng Yun
---
drivers/phy/phy-mt65xx-usb3.c | 99 +--
1 file changed, 96 insertions(+), 3 deletions(-)
diff --git a/drivers/phy/phy-mt65xx-us
when use the default value 8 of RG_USB20_SQTH, the HS receiver
sensitivity test of HQA will fail, set it as 2 to fix up the
issue.
Signed-off-by: Chunfeng Yun
---
drivers/phy/phy-mt65xx-usb3.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/phy/phy-mt65xx-usb3.
On Thu, 2015-12-03 at 14:34 -0500, Waiman Long wrote:
> On 12/02/2015 11:32 PM, Mike Galbraith wrote:
> > Is that with the box booted skew_tick=1?
> I haven't tried that kernel parameter. I will try it to see if it can
> improve the situation. BTW, will there be other undesirable side effects
>
On driver detach, devm_phy_release() will put a refcount to
the phy, so gets a refconut to it before return.
Signed-off-by: Chunfeng Yun
---
drivers/phy/phy-core.c | 21 +++--
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-
On 12/03/2015 08:55 PM, Alexandre Belloni wrote:
> On 03/12/2015 at 19:12:24 -0500, Sasha Levin wrote :
>> > At some point after humans go extinct and robots cotrol the world, dividing
>> > he time64_t by 86400 to extract the days will overflow a 32bit integer,
>> > leading to incorrect conversion
>-Original Message-
>From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
>ow...@vger.kernel.org] On Behalf Of Andy Shevchenko
>Sent: Wednesday, November 25, 2015 10:33 PM
>To: Thomas Gleixner
>Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org; linux-
>p...@vger.kernel
Steven Rostedt writes:
> Xunlei Pang reported a bug in the scheduler code when
> CONFIG_CPUMASK_OFFSTACK is set, several of the cpumasks used by the
> root domains can contain garbage. The code does the following:
>
> memset(rd, 0, sizeof(*rd));
>
> if (!alloc_cpumask_var(&rd->span
Jiri Kosina writes:
> On Thu, 3 Dec 2015, Josh Poimboeuf wrote:
>
>> Calling set_memory_rw() and set_memory_ro() for every iteration of the
>> loop in klp_write_object_relocations() is messy, inefficient, and
>> error-prone.
>>
>> Change all the read-only pages to read-write before the loop and c
Ahoj,
napiste mi na e-mailovou adresu pro podrobnosti o vzájemne spoluprace.
chn.chn.j...@gmail.com
--
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 http://vger.kernel.org/majordomo-info.ht
On 03/12/2015 at 19:12:24 -0500, Sasha Levin wrote :
> At some point after humans go extinct and robots cotrol the world, dividing
> he time64_t by 86400 to extract the days will overflow a 32bit integer,
> leading to incorrect conversion into rtc_time in rtc_time64_to_tm().
>
And at that time, t
Mel Gorman writes:
> On Thu, Dec 03, 2015 at 04:46:53PM +0800, Huang, Ying wrote:
>> Mel Gorman writes:
>>
>> > On Wed, Dec 02, 2015 at 03:15:29PM +0100, Michal Hocko wrote:
>> >> > > I didn't mention this allocation failure because I am not sure it is
>> >> > > really related.
>> >> > >
>> >>
On Fri, Dec 04, 2015 at 02:10:50AM +0100, Andrew Lunn wrote:
> > > FWIW: My initial patch to address the failure worked with the original
> > > DTB.
> >
> > Can I ask what patch are you referring to? I was sidetracked for a while
> > on this issue, but I still see it failing as of v4.4-rc3. I'll
> On Dec 2, 2015, at 16:03, Kees Cook wrote:
>
> 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
Daniel Stone writes:
> Hi,
>
> On 1 December 2015 at 20:35, Eric Anholt wrote:
>> An async pageflip stores the modeset to be done and executes it once
>> the BOs are ready to be displayed. This gets us about 3x performance
>> in full screen rendering with pageflipping.
>
> Looks good, but you'r
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
Hi Sasha,
[auto build test ERROR on abelloni/rtc-next]
[also build test ERROR on v4.4-rc3 next-20151202]
url:
https://github.com/0day-ci/linux/commits/Sasha-Levin/rtc-fix-overflow-and-incorre
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
Hi Sasha,
[auto build test ERROR on abelloni/rtc-next]
[also build test ERROR on v4.4-rc3 next-20151202]
url:
https://github.com/0day-ci/linux/commits/Sasha-Levin/rtc-fix-overflow-and-incorre
On Thu, Dec 03, 2015 at 04:36:28PM -0800, Joe Perches wrote:
> On Thu, 2015-12-03 at 16:29 -0800, Joe Perches wrote:
> > On Thu, 2015-12-03 at 16:13 -0800, Brian Norris wrote:
> > > Ping? I've hit some different false positives today on the same rule.
> > > I'll stop bothering to report them if no
From: Dave Hansen
For protection keys, we need to understand whether protections
should be enforced in software or not. In general, we enforce
protections when working on our own task, but not when on others.
We call these "current" and "foreign" operations.
This introduces two new get_user_pa
1 - 100 of 902 matches
Mail list logo