> > What happens if the root_hpa is dropped by the L0 MMU? I'm not sure
> > what removes it from the shadow EPT list.
>
> That would result in a vmfunc vmexit, which will jump to handle_vmfunc
> and then a call to mmu_alloc_shadow_roots() that will overwrite the shadow
> eptp entry with the new
> > What happens if the root_hpa is dropped by the L0 MMU? I'm not sure
> > what removes it from the shadow EPT list.
>
> That would result in a vmfunc vmexit, which will jump to handle_vmfunc
> and then a call to mmu_alloc_shadow_roots() that will overwrite the shadow
> eptp entry with the new
Answer: No nothing got broken except the driver itself.
On Fri, Jun 30, 2017 at 4:10 PM, David F. wrote:
> Hi,
>
> I have a driver that reads data from a file that has worked from
> kernel 3.x up to 4.9.13. I haven't tried all the other 4.9's or 4.10,
> or 4.11.6 or earlier,
Answer: No nothing got broken except the driver itself.
On Fri, Jun 30, 2017 at 4:10 PM, David F. wrote:
> Hi,
>
> I have a driver that reads data from a file that has worked from
> kernel 3.x up to 4.9.13. I haven't tried all the other 4.9's or 4.10,
> or 4.11.6 or earlier, but in 4.11.7 it's
On 30 June 2017 at 15:58, Vincent Guittot wrote:
> The running state is a subset of runnable state which means that running
> can't be set if runnable (weight) is cleared. There are corner cases
> where the current sched_entity has been already dequeued but
On 30 June 2017 at 15:58, Vincent Guittot wrote:
> The running state is a subset of runnable state which means that running
> can't be set if runnable (weight) is cleared. There are corner cases
> where the current sched_entity has been already dequeued but cfs_rq->curr
> has not been updated yet
The running state is a subset of runnable state which means that running
can't be set if runnable (weight) is cleared. There are corner cases
where the current sched_entity has been already dequeued but cfs_rq->curr
has not been updated yet and still points to the dequeued sched_entity.
If
The running state is a subset of runnable state which means that running
can't be set if runnable (weight) is cleared. There are corner cases
where the current sched_entity has been already dequeued but cfs_rq->curr
has not been updated yet and still points to the dequeued sched_entity.
If
Hi, Andrea
OWL_CPUx_ADDR is the physical address of CPUx wakeup function.
OWL_CPUx_FLAG is a valid flag of OWL_CPUx_ADDR.
After CPUxs are wakeuped by SEV instruction, they will check their own
OWL_CPUx_FLAG register. If the register vlaue is 0x55aa, CPUx will jump to
OWL_CPUx_ADDR to boot up,
Hi, Andrea
OWL_CPUx_ADDR is the physical address of CPUx wakeup function.
OWL_CPUx_FLAG is a valid flag of OWL_CPUx_ADDR.
After CPUxs are wakeuped by SEV instruction, they will check their own
OWL_CPUx_FLAG register. If the register vlaue is 0x55aa, CPUx will jump to
OWL_CPUx_ADDR to boot up,
On Fri, Jun 30, 2017 at 05:17:35PM -0500, Gustavo A. R. Silva wrote:
> Check return value from call to platform_get_irq(),
> so in case of failure print error message and propagate
> the return value.
>
> Signed-off-by: Gustavo A. R. Silva
Acked-by: Nicolin Chen
On Fri, Jun 30, 2017 at 05:17:35PM -0500, Gustavo A. R. Silva wrote:
> Check return value from call to platform_get_irq(),
> so in case of failure print error message and propagate
> the return value.
>
> Signed-off-by: Gustavo A. R. Silva
Acked-by: Nicolin Chen
Thanks
> ---
>
On Fri, 30 Jun 2017, Andreas Dilger wrote:
> On Jun 29, 2017, at 8:25 PM, Mikulas Patocka wrote:
> >
> > The __vmalloc function has a parameter gfp_mask with the allocation flags,
> > however it doesn't fully respect the GFP_NOIO and GFP_NOFS flags. The
> > pages are
On Fri, 30 Jun 2017, Andreas Dilger wrote:
> On Jun 29, 2017, at 8:25 PM, Mikulas Patocka wrote:
> >
> > The __vmalloc function has a parameter gfp_mask with the allocation flags,
> > however it doesn't fully respect the GFP_NOIO and GFP_NOFS flags. The
> > pages are allocated with the
On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann wrote:
> Add a bus level dsm_mask to nvdimm_bus_descriptor to allow the passthru
> calling mechanism to specify a different mask from the cmd_mask.
>
> Populate bus_dsm_mask and use it to filter dsm calls that user can
> make
On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann wrote:
> Add a bus level dsm_mask to nvdimm_bus_descriptor to allow the passthru
> calling mechanism to specify a different mask from the cmd_mask.
>
> Populate bus_dsm_mask and use it to filter dsm calls that user can
> make through the pass thru
On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann wrote:
> Have module parameter override_dsm_mask override the dsm_mask for
> root calls like it does for non-root dsm calls.
>
> Signed-off-by: Jerry Hoemann
> ---
> drivers/acpi/nfit/core.c | 2 ++
> 1
On Fri, Jun 30, 2017 at 9:09 AM, Jerry Hoemann wrote:
> Have module parameter override_dsm_mask override the dsm_mask for
> root calls like it does for non-root dsm calls.
>
> Signed-off-by: Jerry Hoemann
> ---
> drivers/acpi/nfit/core.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git
On Fri, Jun 30, 2017 at 02:00:54PM +1000, Stephen Rothwell wrote:
> Hi Darren,
>
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/platform/x86/sony-laptop.c: In function 'sony_laptop_setup_input':
>
On Fri, Jun 30, 2017 at 02:00:54PM +1000, Stephen Rothwell wrote:
> Hi Darren,
>
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/platform/x86/sony-laptop.c: In function 'sony_laptop_setup_input':
>
On Fri, Jun 30, 2017 at 11:50:52PM +0300, Andy Shevchenko wrote:
> On Fri, Jun 30, 2017 at 9:21 PM, Darren Hart wrote:
> > On Fri, Jun 30, 2017 at 06:58:24PM +0300, Andy Shevchenko wrote:
> >> On Fri, Jun 30, 2017 at 6:45 PM, Arnd Bergmann wrote:
>
> > Will
On Fri, Jun 30, 2017 at 11:50:52PM +0300, Andy Shevchenko wrote:
> On Fri, Jun 30, 2017 at 9:21 PM, Darren Hart wrote:
> > On Fri, Jun 30, 2017 at 06:58:24PM +0300, Andy Shevchenko wrote:
> >> On Fri, Jun 30, 2017 at 6:45 PM, Arnd Bergmann wrote:
>
> > Will you squash it, or shall I?
>
>
On Jun 29, 2017, at 8:25 PM, Mikulas Patocka wrote:
>
> The __vmalloc function has a parameter gfp_mask with the allocation flags,
> however it doesn't fully respect the GFP_NOIO and GFP_NOFS flags. The
> pages are allocated with the specified gfp flags, but the pagetables
On Jun 29, 2017, at 8:25 PM, Mikulas Patocka wrote:
>
> The __vmalloc function has a parameter gfp_mask with the allocation flags,
> however it doesn't fully respect the GFP_NOIO and GFP_NOFS flags. The
> pages are allocated with the specified gfp flags, but the pagetables are
> always allocated
Hey,
On Wed, Jun 28, 2017 at 07:11:59PM +0900, Kunihiko Hayashi wrote:
> Add a thermal driver for on-chip PVT (Process, Voltage and Temperature)
> monitoring unit implemented on UniPhier SoCs. This driver supports
> temperature monitoring and alert function.
>
> Signed-off-by: Kunihiko Hayashi
Hey,
On Wed, Jun 28, 2017 at 07:11:59PM +0900, Kunihiko Hayashi wrote:
> Add a thermal driver for on-chip PVT (Process, Voltage and Temperature)
> monitoring unit implemented on UniPhier SoCs. This driver supports
> temperature monitoring and alert function.
>
> Signed-off-by: Kunihiko Hayashi
On Thu, Jun 22, 2017 at 11:42:03AM +0800, Tao Wang wrote:
> Bind thermal sensor driver for Hi3660.
>
> Signed-off-by: Tao Wang
> Signed-off-by: Leo Yan
> ---
> Changes in v2:
> - rebase changes on linux next
>
>
On Thu, Jun 22, 2017 at 11:42:03AM +0800, Tao Wang wrote:
> Bind thermal sensor driver for Hi3660.
>
> Signed-off-by: Tao Wang
> Signed-off-by: Leo Yan
> ---
> Changes in v2:
> - rebase changes on linux next
>
> arch/arm64/boot/dts/hisilicon/hi3660.dtsi |6 ++
> 1 file changed, 6
Hi, Enric,
On Fri, 2017-06-30 at 10:15 +0200, Enric Balletbo Serra wrote:
> Hi Rui,
>
> 2017-06-30 7:05 GMT+02:00 Zhang Rui :
> >
> > On Thu, 2017-06-29 at 18:50 +0200, Enric Balletbo i Serra wrote:
> > >
> > > Under each thermal zone there is a optional file called
Hi, Enric,
On Fri, 2017-06-30 at 10:15 +0200, Enric Balletbo Serra wrote:
> Hi Rui,
>
> 2017-06-30 7:05 GMT+02:00 Zhang Rui :
> >
> > On Thu, 2017-06-29 at 18:50 +0200, Enric Balletbo i Serra wrote:
> > >
> > > Under each thermal zone there is a optional file called "mode".
> > > Writing
> > >
On Thu, Jun 22, 2017 at 11:42:01AM +0800, Tao Wang wrote:
> This adds documentation of device tree bindings for the
> thermal sensor controller of hi3660 SoC.
>
> Signed-off-by: Tao Wang
> ---
> Changes in v2:
> - remove redundant property
>
>
On Thu, Jun 22, 2017 at 11:42:01AM +0800, Tao Wang wrote:
> This adds documentation of device tree bindings for the
> thermal sensor controller of hi3660 SoC.
>
> Signed-off-by: Tao Wang
> ---
> Changes in v2:
> - remove redundant property
>
> .../devicetree/bindings/thermal/hi3660-thermal.txt
Hey Tao,
On Thu, Jun 22, 2017 at 11:42:02AM +0800, Tao Wang wrote:
> This patch adds the support for thermal sensor of Hi3660 SoC.
> this will register sensors for thermal framework and use device
> tree to bind cooling device.
>
> Signed-off-by: Tao Wang
>
Hey Tao,
On Thu, Jun 22, 2017 at 11:42:02AM +0800, Tao Wang wrote:
> This patch adds the support for thermal sensor of Hi3660 SoC.
> this will register sensors for thermal framework and use device
> tree to bind cooling device.
>
> Signed-off-by: Tao Wang
> Signed-off-by: Leo Yan
> ---
>
> -Original Message-
> From: Paul Elder on Friday, June 30, 2017 7:28 PM
> On 07/01/2017 08:47 AM, Shuah Khan wrote:
> > Convert to TAP13 output using ksft_ api. Child runs tests, increments test
> > counters, and prints test results.
> >
> > Signed-off-by: Shuah Khan
> -Original Message-
> From: Paul Elder on Friday, June 30, 2017 7:28 PM
> On 07/01/2017 08:47 AM, Shuah Khan wrote:
> > Convert to TAP13 output using ksft_ api. Child runs tests, increments test
> > counters, and prints test results.
> >
> > Signed-off-by: Shuah Khan
> > ---
> >
> >
On Fri, Jun 23, 2017 at 10:25:45PM +0200, Stefan Wahren wrote:
>
> > Christophe JAILLET hat am 23. Juni 2017 um
> > 21:44 geschrieben:
> >
> >
> > 'tz' is a valid pointer at this point, so calling PTR_ERR on it is
> > pointless.
> > This 'err = PTR_ERR(tz)'
On Fri, Jun 23, 2017 at 10:25:45PM +0200, Stefan Wahren wrote:
>
> > Christophe JAILLET hat am 23. Juni 2017 um
> > 21:44 geschrieben:
> >
> >
> > 'tz' is a valid pointer at this point, so calling PTR_ERR on it is
> > pointless.
> > This 'err = PTR_ERR(tz)' looks like a cut'n'paste from a few
Hey Mikko,
Sorry for the late answer,
On Fri, Jun 16, 2017 at 02:28:25PM +0300, Mikko Perttunen wrote:
> On Tegra186, the BPMP (Boot and Power Management Processor) exposes an
> interface to thermal sensors on the system-on-chip. This driver
> implements access to the interface. It supports
Hey Mikko,
Sorry for the late answer,
On Fri, Jun 16, 2017 at 02:28:25PM +0300, Mikko Perttunen wrote:
> On Tegra186, the BPMP (Boot and Power Management Processor) exposes an
> interface to thermal sensors on the system-on-chip. This driver
> implements access to the interface. It supports
About this commit in mm:
---
commit c1aca87fb3f84a813fb3dda656bbee583c9c87a3
Author: Alexey Dobriyan
Date: Fri Jun 30 11:02:04 2017 +1000
fs/seq_file.c: delete small-value optimization
num_to_str() optimizes
About this commit in mm:
---
commit c1aca87fb3f84a813fb3dda656bbee583c9c87a3
Author: Alexey Dobriyan
Date: Fri Jun 30 11:02:04 2017 +1000
fs/seq_file.c: delete small-value optimization
num_to_str() optimizes printing small integers
From: Ondrej Zary
When an IRQ arrives during PDMA transfer, pread() and pwrite() return
without waiting for the 53C80 registers to be ready and this ends up
messing up the chip state. This was observed with SONY CDU-55S which is
slow enough to disconnect during
From: Ondrej Zary
Limit PDMA send to 512 B to avoid data corruption on DTC3181E. The
corruption is always the same: one byte missing at the beginning of
a 128 B block. It happens only with slow Quantum LPS 240 drive, not with
faster IBM DORS-32160. It's not clear what
From: Ondrej Zary
When an IRQ arrives during PDMA transfer, pread() and pwrite() return
without waiting for the 53C80 registers to be ready and this ends up
messing up the chip state. This was observed with SONY CDU-55S which is
slow enough to disconnect during 4096-byte reads.
IRQ during PDMA
From: Ondrej Zary
Limit PDMA send to 512 B to avoid data corruption on DTC3181E. The
corruption is always the same: one byte missing at the beginning of
a 128 B block. It happens only with slow Quantum LPS 240 drive, not with
faster IBM DORS-32160. It's not clear what causes this. Documentation
From: Ondrej Zary
The polling loops in pread() and pwrite() can easily become infinite
loops and hang the machine.
Merge the IRQ check into host buffer wait loop and add polling limit.
Also place a limit on polling for 53C80 registers accessibility.
[Use
From: Ondrej Zary
The polling loops in pread() and pwrite() can easily become infinite
loops and hang the machine.
Merge the IRQ check into host buffer wait loop and add polling limit.
Also place a limit on polling for 53C80 registers accessibility.
[Use NCR5380_poll_politely2() for register
From: Ondrej Zary
generic_NCR5380_dma_xfer_len() incorrectly uses cmd->transfersize
which causes rescan-scsi-bus and CD-ROM access to hang the system.
Use cmd->SCp.this_residual instead, like other NCR5380 drivers.
Signed-off-by: Ondrej Zary
Ondrej, would you please test this new series?
Changed since v1:
- PDMA transfer residual is calculated earlier.
- End of DMA flag check is now polled (if there is any residual).
Changed since v2:
- Bail out of transfer loops when Gated IRQ gets asserted.
- Make udelay conditional on board type.
From: Ondrej Zary
generic_NCR5380_dma_xfer_len() incorrectly uses cmd->transfersize
which causes rescan-scsi-bus and CD-ROM access to hang the system.
Use cmd->SCp.this_residual instead, like other NCR5380 drivers.
Signed-off-by: Ondrej Zary
Signed-off-by: Finn Thain
---
Ondrej, would you please test this new series?
Changed since v1:
- PDMA transfer residual is calculated earlier.
- End of DMA flag check is now polled (if there is any residual).
Changed since v2:
- Bail out of transfer loops when Gated IRQ gets asserted.
- Make udelay conditional on board type.
The word "read" may be used to mean "DMA read operation" or
"SCSI READ command", though a READ command implies writing to memory.
Signed-off-by: Finn Thain
---
drivers/scsi/g_NCR5380.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
Signed-off-by: Finn Thain
---
drivers/scsi/g_NCR5380.c | 61 ++--
1 file changed, 28 insertions(+), 33 deletions(-)
diff --git a/drivers/scsi/g_NCR5380.c b/drivers/scsi/g_NCR5380.c
index 911a4300ea51..dedaed2d16e4 100644
The word "read" may be used to mean "DMA read operation" or
"SCSI READ command", though a READ command implies writing to memory.
Signed-off-by: Finn Thain
---
drivers/scsi/g_NCR5380.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/scsi/g_NCR5380.c
Signed-off-by: Finn Thain
---
drivers/scsi/g_NCR5380.c | 61 ++--
1 file changed, 28 insertions(+), 33 deletions(-)
diff --git a/drivers/scsi/g_NCR5380.c b/drivers/scsi/g_NCR5380.c
index 911a4300ea51..dedaed2d16e4 100644
--- a/drivers/scsi/g_NCR5380.c
On Fri, 30 Jun 2017, Ondrej Zary wrote:
> > > No more log spamming on DTC but reads are corrupted even more than
> > > before. The IRQ check after data transfer increases the chance of
> > > catching an IRQ before the buffer could become ready.
> >
> > If we delay the IRQ check, that just means
On Fri, 30 Jun 2017, Ondrej Zary wrote:
> > > No more log spamming on DTC but reads are corrupted even more than
> > > before. The IRQ check after data transfer increases the chance of
> > > catching an IRQ before the buffer could become ready.
> >
> > If we delay the IRQ check, that just means
On 07/01/2017 08:47 AM, Shuah Khan wrote:
> Convert to TAP13 output using ksft_ api. Child runs tests, increments test
> counters, and prints test results.
>
> Signed-off-by: Shuah Khan
> ---
>
> Changes since v1:
> - Add ksft_print_header()
>
>
On 07/01/2017 08:47 AM, Shuah Khan wrote:
> Convert to TAP13 output using ksft_ api. Child runs tests, increments test
> counters, and prints test results.
>
> Signed-off-by: Shuah Khan
> ---
>
> Changes since v1:
> - Add ksft_print_header()
>
> tools/testing/selftests/kcmp/kcmp_test.c | 48
If a process is in a mountns and has symbols in /tmp/perf-.map,
look first in the namespace using the tgid for the pidns that the
process might be in. If the map isn't found there, try looking in
the mountns where perf is running, and use the tgid that's appropriate
for perf's pid namespace. If
If a process is in a mountns and has symbols in /tmp/perf-.map,
look first in the namespace using the tgid for the pidns that the
process might be in. If the map isn't found there, try looking in
the mountns where perf is running, and use the tgid that's appropriate
for perf's pid namespace. If
Teach perf how to resolve symbols from binaries that are in a different
mount namespace from the tool. This allows perf to generate meaningful
stack traces even if the binary resides in a different mount namespace
from the tool.
Signed-off-by: Krister Johansen
---
If a stripped binary is placed in the cache, the user is in a situation
where there's a cached elf file present, but it doesn't have any symtab
to use for name resolution. Grab the debuginfo for binaries that don't
end in .ko. This yields a better chance of resolving symbols from
older traces.
The perf top command needs to unshare its fs from the helper threads
in order to successfully setns(2) during its symbol lookup. It also
needs to impelement a force flag to ignore ownership of perf-.map
files.
Signed-off-by: Krister Johansen
---
Update the perf documentation to describe the --target-ns option to
probe and buildid-cache. Note the existence of the new --force flag
to top.
Signed-off-by: Krister Johansen
---
tools/perf/Documentation/perf-buildid-cache.txt | 5 +
Teach perf how to resolve symbols from binaries that are in a different
mount namespace from the tool. This allows perf to generate meaningful
stack traces even if the binary resides in a different mount namespace
from the tool.
Signed-off-by: Krister Johansen
---
tools/perf/util/dso.c
If a stripped binary is placed in the cache, the user is in a situation
where there's a cached elf file present, but it doesn't have any symtab
to use for name resolution. Grab the debuginfo for binaries that don't
end in .ko. This yields a better chance of resolving symbols from
older traces.
The perf top command needs to unshare its fs from the helper threads
in order to successfully setns(2) during its symbol lookup. It also
needs to impelement a force flag to ignore ownership of perf-.map
files.
Signed-off-by: Krister Johansen
---
tools/perf/builtin-top.c | 15 +++
1
Update the perf documentation to describe the --target-ns option to
probe and buildid-cache. Note the existence of the new --force flag
to top.
Signed-off-by: Krister Johansen
---
tools/perf/Documentation/perf-buildid-cache.txt | 5 +
tools/perf/Documentation/perf-probe.txt | 5
Teaches perf how to place a uprobe on a file that's in a different mount
namespace. The user must add the probe using the --target-ns argument
to perf probe. Once it has been placed, it may be recorded against
without further namespace-specific commands.
Signed-off-by: Krister Johansen
This patch set is similar to a set of features I implemented for bcc
back in April. At a high-level it does the following:
- Allow the tracing tools to resolve symbols if the traced process has a
binary that is in a different mount namespace from perf.
- Allow the perf-.map files to live
Teach buildid-cache how to add, remove, and update binary objects from
other mount namespaces. Allow probe events tracing binaries in
different namespaces to add their objects to the probe and build-id
caches too. As a handy side effect, this also lets us access SDT probes
in binaries from
Teaches perf how to place a uprobe on a file that's in a different mount
namespace. The user must add the probe using the --target-ns argument
to perf probe. Once it has been placed, it may be recorded against
without further namespace-specific commands.
Signed-off-by: Krister Johansen
---
This patch set is similar to a set of features I implemented for bcc
back in April. At a high-level it does the following:
- Allow the tracing tools to resolve symbols if the traced process has a
binary that is in a different mount namespace from perf.
- Allow the perf-.map files to live
Teach buildid-cache how to add, remove, and update binary objects from
other mount namespaces. Allow probe events tracing binaries in
different namespaces to add their objects to the probe and build-id
caches too. As a handy side effect, this also lets us access SDT probes
in binaries from
On 6/30/17 5:57 PM, Jerome Glisse wrote:
On Fri, Jun 30, 2017 at 04:19:25PM -0700, Evgeny Baskakov wrote:
Hi Jerome,
It seems that the kernel can pass 0 in src_pfns for pages that it cannot
migrate (i.e. the kernel knows that they cannot migrate prior to calling
alloc_and_copy).
So, a zero
On 6/30/17 5:57 PM, Jerome Glisse wrote:
On Fri, Jun 30, 2017 at 04:19:25PM -0700, Evgeny Baskakov wrote:
Hi Jerome,
It seems that the kernel can pass 0 in src_pfns for pages that it cannot
migrate (i.e. the kernel knows that they cannot migrate prior to calling
alloc_and_copy).
So, a zero
On (06/30/17 10:45), Steven Rostedt wrote:
> On Fri, 30 Jun 2017 23:28:51 +0900
> Sergey Senozhatsky wrote:
>
> > I guess the question was, a knob that would determine what happens after
> > current wakes up printk_kthread -- does it stay in console_unlock()
On (06/30/17 10:45), Steven Rostedt wrote:
> On Fri, 30 Jun 2017 23:28:51 +0900
> Sergey Senozhatsky wrote:
>
> > I guess the question was, a knob that would determine what happens after
> > current wakes up printk_kthread -- does it stay in console_unlock() and
> > wait for new console_sem
Fathi Boudra writes:
> On 30 June 2017 at 05:20, Bamvor Zhang Jian
> wrote:
>> On 29 June 2017 at 19:39, Fathi Boudra wrote:
>>> On 29 June 2017 at 12:01, Michael Ellerman wrote:
Fathi
Fathi Boudra writes:
> On 30 June 2017 at 05:20, Bamvor Zhang Jian
> wrote:
>> On 29 June 2017 at 19:39, Fathi Boudra wrote:
>>> On 29 June 2017 at 12:01, Michael Ellerman wrote:
Fathi Boudra writes:
> Fix hardcoded and misplaced libmount headers. Use pkg-config instead to
On Tue, Jun 13, 2017 at 06:16:21PM -0500, Grygorii Strashko wrote:
> There are two reasons for this change:
> 1) enabling of HW_TS_PUSH events as suggested by Richard Cochran and
> discussed in [1]
> 2) fixing an TX timestamping miss issue which happens with low speed
> ethernet connections and
On Tue, Jun 13, 2017 at 06:16:21PM -0500, Grygorii Strashko wrote:
> There are two reasons for this change:
> 1) enabling of HW_TS_PUSH events as suggested by Richard Cochran and
> discussed in [1]
> 2) fixing an TX timestamping miss issue which happens with low speed
> ethernet connections and
On Fri, Jun 30, 2017 at 04:19:25PM -0700, Evgeny Baskakov wrote:
> Hi Jerome,
>
> It seems that the kernel can pass 0 in src_pfns for pages that it cannot
> migrate (i.e. the kernel knows that they cannot migrate prior to calling
> alloc_and_copy).
>
> So, a zero in src_pfns can mean either "the
On Fri, Jun 30, 2017 at 04:19:25PM -0700, Evgeny Baskakov wrote:
> Hi Jerome,
>
> It seems that the kernel can pass 0 in src_pfns for pages that it cannot
> migrate (i.e. the kernel knows that they cannot migrate prior to calling
> alloc_and_copy).
>
> So, a zero in src_pfns can mean either "the
On 6/30/2017 6:08 AM, Andrea Arcangeli wrote:
On Fri, Jun 30, 2017 at 11:47:35AM +0200, Michal Hocko wrote:
[...]
As an aside, I rememeber that prior to MADV_FREE there was long
discussion about lazy freeing of memory from userspace. Some users
wanted to be signalled when their memory was
On 06/20, Dong Aisheng wrote:
> Hi Stephen,
>
> On Mon, Jun 19, 2017 at 06:45:12PM -0700, Stephen Boyd wrote:
> > On 05/15, Dong Aisheng wrote:
> > > ---
> > > drivers/clk/clk-divider.c| 2 ++
> > > include/linux/clk-provider.h | 4
> > > 2 files changed, 6 insertions(+)
> > >
> > >
On 6/30/2017 6:08 AM, Andrea Arcangeli wrote:
On Fri, Jun 30, 2017 at 11:47:35AM +0200, Michal Hocko wrote:
[...]
As an aside, I rememeber that prior to MADV_FREE there was long
discussion about lazy freeing of memory from userspace. Some users
wanted to be signalled when their memory was
On 06/20, Dong Aisheng wrote:
> Hi Stephen,
>
> On Mon, Jun 19, 2017 at 06:45:12PM -0700, Stephen Boyd wrote:
> > On 05/15, Dong Aisheng wrote:
> > > ---
> > > drivers/clk/clk-divider.c| 2 ++
> > > include/linux/clk-provider.h | 4
> > > 2 files changed, 6 insertions(+)
> > >
> > >
Hi,
On Thu, Jun 29, 2017 at 02:10:09PM +0200, Benjamin Tissoires wrote:
> [...]
>
> + /* get design capacity */
> + ret = i2c_smbus_read_word_data(client,
> +MSHW0011_BAT0_REG_DESIGN_CAPACITY);
> + if (ret < 0) {
> + dev_err(>dev, "Error
Hi,
On Thu, Jun 29, 2017 at 02:10:09PM +0200, Benjamin Tissoires wrote:
> [...]
>
> + /* get design capacity */
> + ret = i2c_smbus_read_word_data(client,
> +MSHW0011_BAT0_REG_DESIGN_CAPACITY);
> + if (ret < 0) {
> + dev_err(>dev, "Error
> > Sysfs "badblocks" information may be updated during run-time that:
> > - MCE, SCI, and sysfs "scrub" may add new bad blocks
> > - Writes and ioctl() may clear bad blocks
> >
> > Add support to send sysfs notifications to sysfs "badblocks" file
> > under region and pmem directories when their
> > Sysfs "badblocks" information may be updated during run-time that:
> > - MCE, SCI, and sysfs "scrub" may add new bad blocks
> > - Writes and ioctl() may clear bad blocks
> >
> > Add support to send sysfs notifications to sysfs "badblocks" file
> > under region and pmem directories when their
On 06/20, Dong Aisheng wrote:
> On Mon, Jun 19, 2017 at 06:59:17PM -0700, Stephen Boyd wrote:
> > On 05/15, Dong Aisheng wrote:
> > > +
> > > + if (clk_pllv4_is_enabled(hw)) {
> > > + WARN(1, "clk_pllv4: can't change rate when pll is enabled");
> > > + return -EINVAL;
> >
> > Sad,
On 06/20, Dong Aisheng wrote:
> On Mon, Jun 19, 2017 at 06:59:17PM -0700, Stephen Boyd wrote:
> > On 05/15, Dong Aisheng wrote:
> > > +
> > > + if (clk_pllv4_is_enabled(hw)) {
> > > + WARN(1, "clk_pllv4: can't change rate when pll is enabled");
> > > + return -EINVAL;
> >
> > Sad,
On Fri, 30 Jun 2017, Michal Hocko wrote:
> On Fri 30-06-17 14:11:57, Mikulas Patocka wrote:
> >
> >
> > On Fri, 30 Jun 2017, Michal Hocko wrote:
> >
> > > On Thu 29-06-17 22:25:09, Mikulas Patocka wrote:
> > > > The __vmalloc function has a parameter gfp_mask with the allocation
> > > >
On Fri, 30 Jun 2017, Michal Hocko wrote:
> On Fri 30-06-17 14:11:57, Mikulas Patocka wrote:
> >
> >
> > On Fri, 30 Jun 2017, Michal Hocko wrote:
> >
> > > On Thu 29-06-17 22:25:09, Mikulas Patocka wrote:
> > > > The __vmalloc function has a parameter gfp_mask with the allocation
> > > >
On 06/21, A.s. Dong wrote:
> > -Original Message-
> > From: Stephen Boyd [mailto:sb...@codeaurora.org]
> > Sent: Wednesday, June 21, 2017 4:42 AM
> > To: Dong Aisheng
> > Cc: A.s. Dong; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> > linux-arm-ker...@lists.infradead.org;
On 06/21, A.s. Dong wrote:
> > -Original Message-
> > From: Stephen Boyd [mailto:sb...@codeaurora.org]
> > Sent: Wednesday, June 21, 2017 4:42 AM
> > To: Dong Aisheng
> > Cc: A.s. Dong; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> > linux-arm-ker...@lists.infradead.org;
1 - 100 of 1590 matches
Mail list logo