Re: runtime regression with "x86/mm/pat: Emulate PAT when it is disabled"

On Thu, 2016-03-10 at 09:42 -0500, Paul Gortmaker wrote: > [Re: runtime regression with "x86/mm/pat: Emulate PAT when it is > disabled"] On 07/03/2016 (Mon 18:35) Toshi Kani wrote: > > > On Mon, 2016-03-07 at 17:56 -0700, Toshi Kani wrote: > > [...] > > > And also an output of /proc/cpuinfo,

Re: [PATCH] perf tool: Build jitdump only on supported archs

Em Thu, Mar 10, 2016 at 10:32:29AM +0100, Jiri Olsa escreveu: > On Mon, Mar 07, 2016 at 04:44:36PM -0300, Arnaldo Carvalho de Melo wrote: > > SNIP > > > > > Adrian Hunter (5): > > perf inject: Hit all DSOs for AUX data in JIT

Re: [PATCH 01/18] mm: Make mmap_sem for write waits killable for mm syscalls

On Thu 10-03-16 16:47:16, Vlastimil Babka wrote: > On 02/29/2016 02:26 PM, Michal Hocko wrote: > >From: Michal Hocko > > > >This is the first step in making mmap_sem write holders killable. It > > s/holders/waiters/? right. Fixed > >focuses on the trivial ones which are

Re: [PATCH 01/18] mm: Make mmap_sem for write waits killable for mm syscalls

On Thu 10-03-16 16:47:16, Vlastimil Babka wrote: > On 02/29/2016 02:26 PM, Michal Hocko wrote: > >From: Michal Hocko > > > >This is the first step in making mmap_sem write holders killable. It > > s/holders/waiters/? right. Fixed > >focuses on the trivial ones which are taking the lock early

Re: runtime regression with "x86/mm/pat: Emulate PAT when it is disabled"

On Thu, 2016-03-10 at 09:42 -0500, Paul Gortmaker wrote: > [Re: runtime regression with "x86/mm/pat: Emulate PAT when it is > disabled"] On 07/03/2016 (Mon 18:35) Toshi Kani wrote: > > > On Mon, 2016-03-07 at 17:56 -0700, Toshi Kani wrote: > > [...] > > > And also an output of /proc/cpuinfo,

Re: [PATCH] perf tool: Build jitdump only on supported archs

Em Thu, Mar 10, 2016 at 10:32:29AM +0100, Jiri Olsa escreveu: > On Mon, Mar 07, 2016 at 04:44:36PM -0300, Arnaldo Carvalho de Melo wrote: > > SNIP > > > > > Adrian Hunter (5): > > perf inject: Hit all DSOs for AUX data in JIT

Re: [PATCH v7] scsi: ufs: add ioctl interface for query request

> On Wed, Mar 09, 2016 at 08:52:59PM -, yga...@codeaurora.org wrote: >> > On Wed, Mar 09, 2016 at 07:09:49PM -, yga...@codeaurora.org wrote: >> >> > On Wed, Mar 09, 2016 at 04:11:33PM +0200, Yaniv Gardi wrote: >> >> >> This patch exposes the ioctl interface for UFS driver via SCSI >>

Re: [PATCH v7] scsi: ufs: add ioctl interface for query request

> On Wed, Mar 09, 2016 at 08:52:59PM -, yga...@codeaurora.org wrote: >> > On Wed, Mar 09, 2016 at 07:09:49PM -, yga...@codeaurora.org wrote: >> >> > On Wed, Mar 09, 2016 at 04:11:33PM +0200, Yaniv Gardi wrote: >> >> >> This patch exposes the ioctl interface for UFS driver via SCSI >>

Re: [RFC][PATCH v2 1/2] printk: Make printk() completely async

On (03/10/16 10:27), Jan Kara wrote: [..] > So I think this should definitely stay as a separate patch since it > possibly changes user visible behavior and sometimes blocking may be > actually desirable for userspace. I don't have that strong opinion whether > it should be in a separate patch set

Re: [RFC][PATCH v2 1/2] printk: Make printk() completely async

On (03/10/16 10:27), Jan Kara wrote: [..] > So I think this should definitely stay as a separate patch since it > possibly changes user visible behavior and sometimes blocking may be > actually desirable for userspace. I don't have that strong opinion whether > it should be in a separate patch set

Re: [PATCH 01/18] mm: Make mmap_sem for write waits killable for mm syscalls

On 02/29/2016 02:26 PM, Michal Hocko wrote: From: Michal Hocko This is the first step in making mmap_sem write holders killable. It s/holders/waiters/? focuses on the trivial ones which are taking the lock early after entering the syscall and they are not changing state

Re: [PATCH] block: fix possible NULL dereference

On 03/10/2016 04:39 AM, Sudip Mukherjee wrote: We were checking for iter to be NULL after dereferencing it. Lets first check it and then use it. Nobody calls it with iter == NULL, I think we should just kill the !iter check -- Jens Axboe

Re: Got FPU related warning on Intel Quark during boot

perly initialized and FPU context in the signal handler is wrong too. Linux 3.8.7: /root@galileo:~# ./fpu f is 10.00 g is 10.10 Double value is 0.00 Double value is 0.10 Double value is 0.20 ^Chandler value of variable is 0.30 Double value is 0.30 Double value is 0.40 Lin

Re: [PATCH 01/18] mm: Make mmap_sem for write waits killable for mm syscalls

On 02/29/2016 02:26 PM, Michal Hocko wrote: From: Michal Hocko This is the first step in making mmap_sem write holders killable. It s/holders/waiters/? focuses on the trivial ones which are taking the lock early after entering the syscall and they are not changing state before. Therefore

Re: [PATCH] block: fix possible NULL dereference

On 03/10/2016 04:39 AM, Sudip Mukherjee wrote: We were checking for iter to be NULL after dereferencing it. Lets first check it and then use it. Nobody calls it with iter == NULL, I think we should just kill the !iter check -- Jens Axboe

Re: Got FPU related warning on Intel Quark during boot

ng too. Linux 3.8.7: /root@galileo:~# ./fpu f is 10.00 g is 10.10 Double value is 0.00 Double value is 0.10 Double value is 0.20 ^Chandler value of variable is 0.30 Double value is 0.30 Double value is 0.40 Linux-next + Boris' fix: root@galileo:~# ./fpu f is -n

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On 03/10/2016 11:31 PM, Paolo Bonzini wrote: On 10/03/2016 16:26, Paolo Bonzini wrote: Compared to smp_load_acquire(), smp_mb() adds an ordering between stores and loads. Here, the ordering is load-store, hence... Yes, this is why i put smp_mb() in the code. :)

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On 03/10/2016 11:31 PM, Paolo Bonzini wrote: On 10/03/2016 16:26, Paolo Bonzini wrote: Compared to smp_load_acquire(), smp_mb() adds an ordering between stores and loads. Here, the ordering is load-store, hence... Yes, this is why i put smp_mb() in the code. :)

[PATCH v8 14/17] scsi: ufs: add device quirk delay before putting UFS rails in LPM

We put the UFS device in sleep state & UFS link in hibern8 state during runtime suspend. After this we put all the UFS rails in low power modes immediately but it seems some devices may still draw more than sleep current from UFS rails (especially from VCCQ rail) at-least for 500us. To avoid this

[PATCH v8 08/17] scsi: ufs: make error handling bit faster

UFS driver's error handler forcefully tries to clear all the pending requests. For each pending request in the queue, it waits 1 sec for it to get cleared. If we have multiple requests in the queue then it's possible that we might end up waiting for those many seconds before resetting the host.

[PATCH v8 14/17] scsi: ufs: add device quirk delay before putting UFS rails in LPM

We put the UFS device in sleep state & UFS link in hibern8 state during runtime suspend. After this we put all the UFS rails in low power modes immediately but it seems some devices may still draw more than sleep current from UFS rails (especially from VCCQ rail) at-least for 500us. To avoid this

[PATCH v8 08/17] scsi: ufs: make error handling bit faster

UFS driver's error handler forcefully tries to clear all the pending requests. For each pending request in the queue, it waits 1 sec for it to get cleared. If we have multiple requests in the queue then it's possible that we might end up waiting for those many seconds before resetting the host.

[PATCH v8 10/17] scsi: ufs: add retry for query descriptors

Query commands have 100ms timeout and it may timeout if they are issued in parallel to ongoing read/write SCSI commands, this change adds the retry (max: 10) in case command timeouts. Reviewed-by: Hannes Reinecke Signed-off-by: Subhash Jadavani

[PATCH v8 07/17] scsi: ufs: disable vccq if it's not needed by UFS device

Some UFS devices don't require VCCQ rail for device operations hence this change adds support to recognize such devices and remove vote for the unused VCCQ rail. Reviewed-by: Hannes Reinecke Signed-off-by: Subhash Jadavani Signed-off-by: Yaniv Gardi

[PATCH v8 16/17] scsi: ufs-qcom: enable/disable the device ref clock

This change enables the device ref clock before changing to HS mode and disables it if entered to PWM mode. Reviewed-by: Gilad Broner Signed-off-by: Yaniv Gardi --- drivers/scsi/ufs/ufs-qcom.c | 12 drivers/scsi/ufs/ufshcd.h | 9

[PATCH v8 05/17] scsi: ufs: add support to read device and string descriptors

This change adds support to read device descriptor and string descriptor from a UFS device Reviewed-by: Gilad Broner Reviewed-by: Hannes Reinecke Signed-off-by: Raviv Shvili Signed-off-by: Yaniv Gardi ---

[PATCH v8 12/17] scsi: ufs: tune UniPro parameters to optimize hibern8 exit time

Optimal values of local UniPro parameters like PA_Hibern8Time & PA_TActivate can help reduce the hibern8 exit latency. If both host and device supports UniPro ver1.6 or later, these parameters will be automatically tuned during link startup itself. But if either host or device doesn't support

[PATCH v8 06/17] scsi: ufs: separate device and host quirks

Currently we use the host quirks mechanism in order to handle both device and host controller quirks. In order to support various of UFS devices we should separate handling the device quirks from the host controller's. Reviewed-by: Gilad Broner Reviewed-by: Hannes

[PATCH v8 03/17] scsi: ufs: implement scsi host timeout handler

A race condition exists between request requeueing and scsi layer error handling: When UFS driver queuecommand returns a busy status for a request, it will be requeued and its tag will be freed and set to -1. At the same time it is possible that the request will timeout and scsi layer will start

[PATCH v8 10/17] scsi: ufs: add retry for query descriptors

Query commands have 100ms timeout and it may timeout if they are issued in parallel to ongoing read/write SCSI commands, this change adds the retry (max: 10) in case command timeouts. Reviewed-by: Hannes Reinecke Signed-off-by: Subhash Jadavani Signed-off-by: Yaniv Gardi ---

[PATCH v8 07/17] scsi: ufs: disable vccq if it's not needed by UFS device

Some UFS devices don't require VCCQ rail for device operations hence this change adds support to recognize such devices and remove vote for the unused VCCQ rail. Reviewed-by: Hannes Reinecke Signed-off-by: Subhash Jadavani Signed-off-by: Yaniv Gardi --- drivers/scsi/ufs/ufs.h| 1 +

[PATCH v8 16/17] scsi: ufs-qcom: enable/disable the device ref clock

This change enables the device ref clock before changing to HS mode and disables it if entered to PWM mode. Reviewed-by: Gilad Broner Signed-off-by: Yaniv Gardi --- drivers/scsi/ufs/ufs-qcom.c | 12 drivers/scsi/ufs/ufshcd.h | 9 + 2 files changed, 21 insertions(+)

[PATCH v8 05/17] scsi: ufs: add support to read device and string descriptors

This change adds support to read device descriptor and string descriptor from a UFS device Reviewed-by: Gilad Broner Reviewed-by: Hannes Reinecke Signed-off-by: Raviv Shvili Signed-off-by: Yaniv Gardi --- drivers/scsi/ufs/ufs.h| 1 + drivers/scsi/ufs/ufshcd.c | 88

[PATCH v8 12/17] scsi: ufs: tune UniPro parameters to optimize hibern8 exit time

Optimal values of local UniPro parameters like PA_Hibern8Time & PA_TActivate can help reduce the hibern8 exit latency. If both host and device supports UniPro ver1.6 or later, these parameters will be automatically tuned during link startup itself. But if either host or device doesn't support

[PATCH v8 06/17] scsi: ufs: separate device and host quirks

Currently we use the host quirks mechanism in order to handle both device and host controller quirks. In order to support various of UFS devices we should separate handling the device quirks from the host controller's. Reviewed-by: Gilad Broner Reviewed-by: Hannes Reinecke Signed-off-by: Raviv

[PATCH v8 03/17] scsi: ufs: implement scsi host timeout handler

A race condition exists between request requeueing and scsi layer error handling: When UFS driver queuecommand returns a busy status for a request, it will be requeued and its tag will be freed and set to -1. At the same time it is possible that the request will timeout and scsi layer will start

[PATCH v4 2/2] power: reset: at91-shdwc: add new shutdown controller driver

Sama5d2 SoC has a completely new shutdown controller with new features and register layout. It thus makes sense to add a new driver for this new peripheral. This driver is Device Tree only and handles events from the wake-up pin and the RTC. As the register layout may change in the future, so

[PATCH v4 2/2] power: reset: at91-shdwc: add new shutdown controller driver

Sama5d2 SoC has a completely new shutdown controller with new features and register layout. It thus makes sense to add a new driver for this new peripheral. This driver is Device Tree only and handles events from the wake-up pin and the RTC. As the register layout may change in the future, so

[PATCH] net: macb: fix default configuration for GMAC on AT91

On AT91 SoCs, the User Register (USRIO) exposes a switch to configure the "Reduced" or "Traditional" version of the Media Independent Interface (RMII vs. MII or RGMII vs. GMII). As on the older EMAC version, on GMAC, this switch is set by default to the non-reduced type of interface, so use the

[PATCH v8 09/17] scsi: ufs: add error recovery after DL NAC error

Some vendor's UFS device sends back to back NACs for the DL data frames causing the host controller to raise the DFES error status. Sometimes such UFS devices send back to back NAC without waiting for new retransmitted DL frame from the host and in such cases it might be possible the Host UniPro

[PATCH] net: macb: fix default configuration for GMAC on AT91

On AT91 SoCs, the User Register (USRIO) exposes a switch to configure the "Reduced" or "Traditional" version of the Media Independent Interface (RMII vs. MII or RGMII vs. GMII). As on the older EMAC version, on GMAC, this switch is set by default to the non-reduced type of interface, so use the

[PATCH v8 09/17] scsi: ufs: add error recovery after DL NAC error

Some vendor's UFS device sends back to back NACs for the DL data frames causing the host controller to raise the DFES error status. Sometimes such UFS devices send back to back NAC without waiting for new retransmitted DL frame from the host and in such cases it might be possible the Host UniPro

[PATCH v8 17/17] scsi: ufs-qcom: add printouts of testbus debug registers

This change adds printouts of testbus and debug registers. Reviewed-by: Gilad Broner Signed-off-by: Yaniv Gardi --- drivers/scsi/ufs/ufs-qcom.c | 77 + drivers/scsi/ufs/ufs-qcom.h | 9 ++ 2 files

[PATCH v8 17/17] scsi: ufs-qcom: add printouts of testbus debug registers

This change adds printouts of testbus and debug registers. Reviewed-by: Gilad Broner Signed-off-by: Yaniv Gardi --- drivers/scsi/ufs/ufs-qcom.c | 77 + drivers/scsi/ufs/ufs-qcom.h | 9 ++ 2 files changed, 86 insertions(+) diff --git

[PATCH v8 02/17] scsi: ufs: avoid spurious UFS host controller interrupts

When control reaches to Linux UFS driver during UFS boot mode, UFS host controller interrupt status/enable registers may have left over settings. In order to avoid any spurious interrupts due to these left overs, it's important to clear these interrupt status/enable registers before enabling UFS

[PATCH v8 11/17] scsi: ufs: handle non spec compliant bkops behaviour by device

We are seeing that some devices are raising the urgent bkops exception events even when BKOPS status doesn't indicate performace impacted or critical. Handle these device by determining their urgent bkops status at runtime. Reviewed-by: Hannes Reinecke Signed-off-by: Subhash

[PATCH v8 02/17] scsi: ufs: avoid spurious UFS host controller interrupts

When control reaches to Linux UFS driver during UFS boot mode, UFS host controller interrupt status/enable registers may have left over settings. In order to avoid any spurious interrupts due to these left overs, it's important to clear these interrupt status/enable registers before enabling UFS

[PATCH v8 11/17] scsi: ufs: handle non spec compliant bkops behaviour by device

We are seeing that some devices are raising the urgent bkops exception events even when BKOPS status doesn't indicate performace impacted or critical. Handle these device by determining their urgent bkops status at runtime. Reviewed-by: Hannes Reinecke Signed-off-by: Subhash Jadavani

[PATCH v4 1/2] ARM: dts: at91: shdwc binding: add new shutdown controller documentation

The new shutdown controller compatible with sama5d2 has a new binding documentation and properties. Signed-off-by: Nicolas Ferre Cc: devicet...@vger.kernel.org Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland

[PATCH v4 0/2] power: reset: support for Atmel alternative Shutdown Controller

This is a series to add driver for a new Atmel Shutdown Controller. This new IP is extensible and some features will be added later (see the TODO section). Its extensible nature led to write a new binding so that wake-up sources can be described easily. Changes in v4: - change property to

[PATCH v8 04/17] scsi: ufs: verify hba controller hce reg value

Sometimes due to hw issues it takes some time to the host controller register to update. In order to verify the register has updated, a polling is done until its value is set. In addition the functions ufshcd_hba_stop() and ufshcd_wait_for_register() was updated with an additional input

[PATCH v8 15/17] scsi: ufs-qcom: set PA_Local_TX_LCC_Enable before link startup

Some UFS devices (and may be host) have issues if LCC is enabled. So we are setting PA_Local_TX_LCC_Enable to 0 before link startup which will make sure that both host and device TX LCC are disabled once link startup is completed. Reviewed-by: Gilad Broner Signed-off-by:

[PATCH v4 1/2] ARM: dts: at91: shdwc binding: add new shutdown controller documentation

The new shutdown controller compatible with sama5d2 has a new binding documentation and properties. Signed-off-by: Nicolas Ferre Cc: devicet...@vger.kernel.org Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian Campbell --- Changes in v4: - change property to debounce-delay-us so that

[PATCH v4 0/2] power: reset: support for Atmel alternative Shutdown Controller

This is a series to add driver for a new Atmel Shutdown Controller. This new IP is extensible and some features will be added later (see the TODO section). Its extensible nature led to write a new binding so that wake-up sources can be described easily. Changes in v4: - change property to

[PATCH v8 04/17] scsi: ufs: verify hba controller hce reg value

Sometimes due to hw issues it takes some time to the host controller register to update. In order to verify the register has updated, a polling is done until its value is set. In addition the functions ufshcd_hba_stop() and ufshcd_wait_for_register() was updated with an additional input

[PATCH v8 15/17] scsi: ufs-qcom: set PA_Local_TX_LCC_Enable before link startup

Some UFS devices (and may be host) have issues if LCC is enabled. So we are setting PA_Local_TX_LCC_Enable to 0 before link startup which will make sure that both host and device TX LCC are disabled once link startup is completed. Reviewed-by: Gilad Broner Signed-off-by: Yaniv Gardi ---

[PATCH v8 00/17] add fixes, device quirks, error recovery,

V8: fixed cyclic dependency by removing ufs_quirk.c that was previously added in V7 06/17, and moving its code into ufshcd.c V7: updated patches with "Reviewed-by" and "Acked-by" tags V6: as per comment, patch 15/15 in V5 was divided into 3 patches in V6 V5: as per comment, patch 05/14 in V4,

[PATCH v8 00/17] add fixes, device quirks, error recovery,

V8: fixed cyclic dependency by removing ufs_quirk.c that was previously added in V7 06/17, and moving its code into ufshcd.c V7: updated patches with "Reviewed-by" and "Acked-by" tags V6: as per comment, patch 15/15 in V5 was divided into 3 patches in V6 V5: as per comment, patch 05/14 in V4,

[PATCH v8 13/17] scsi: ufs: fix leakage during link off state

Currently when we try to put the link in off/disabled state during suspend, it seems link is not being kept in low power mode. This patch fixes the issue by putting the link in hibern8 first (so device also puts the link in low power mode) and then stop the host controller. Reviewed-by: Hannes

[PATCH v8 01/17] scsi: ufs-qcom: add number of lanes per direction

Different platform may have different number of lanes for the UFS link. Add parameter to device tree specifying how many lanes should be configured for the UFS link. Reviewed-by: Hannes Reinecke Acked-by: Rob Herring Signed-off-by: Gilad Broner

[PATCH v8 13/17] scsi: ufs: fix leakage during link off state

Currently when we try to put the link in off/disabled state during suspend, it seems link is not being kept in low power mode. This patch fixes the issue by putting the link in hibern8 first (so device also puts the link in low power mode) and then stop the host controller. Reviewed-by: Hannes

[PATCH v8 01/17] scsi: ufs-qcom: add number of lanes per direction

Different platform may have different number of lanes for the UFS link. Add parameter to device tree specifying how many lanes should be configured for the UFS link. Reviewed-by: Hannes Reinecke Acked-by: Rob Herring Signed-off-by: Gilad Broner Signed-off-by: Yaniv Gardi ---

Re: [PATCH v7 06/17] scsi: ufs: separate device and host quirks

Martin, the only way i can avoid the circular dependency is to move the routines from ufs_quirks.c into ufshcd.c. i will upload V8 soon thanks, Yaniv >> "Yaniv" == Yaniv Gardi writes: > > Yaniv> Currently we use the host quirks mechanism in order to handle > Yaniv>

Re: [PATCH 0/2 v6] printk, Add monotonic and real printk timestamps

On Thu, 10 Mar 2016, Petr Mladek wrote: > On Tue 2016-03-08 06:03:24, Prarit Bhargava wrote: > > > > > > On 03/08/2016 02:59 AM, Thomas Gleixner wrote: > > > On Tue, 23 Feb 2016, Prarit Bhargava wrote: > > > > > >> This patchset adds monotonic and real printk timestamps. The first patch > > >>

Re: [PATCH v7 06/17] scsi: ufs: separate device and host quirks

Martin, the only way i can avoid the circular dependency is to move the routines from ufs_quirks.c into ufshcd.c. i will upload V8 soon thanks, Yaniv >> "Yaniv" == Yaniv Gardi writes: > > Yaniv> Currently we use the host quirks mechanism in order to handle > Yaniv> both device and host

Re: [PATCH 0/2 v6] printk, Add monotonic and real printk timestamps

On Thu, 10 Mar 2016, Petr Mladek wrote: > On Tue 2016-03-08 06:03:24, Prarit Bhargava wrote: > > > > > > On 03/08/2016 02:59 AM, Thomas Gleixner wrote: > > > On Tue, 23 Feb 2016, Prarit Bhargava wrote: > > > > > >> This patchset adds monotonic and real printk timestamps. The first patch > > >>

Re: [PATCH] media: fix !CONFIG_MEDIA_CONTROLLER compile error for v4l_change_media_source()

gt; https://github.com/0day-ci/linux/commits/Shuah-Khan/media-add-change_source-handler-support/20160310-131140 > base: git://linuxtv.org/media_tree.git master > config: x86_64-rhel (attached as .config) > reproduce: > # save the attached .config to linux build tree >

Re: [PATCH] media: fix !CONFIG_MEDIA_CONTROLLER compile error for v4l_change_media_source()

i/linux/commits/Shuah-Khan/media-add-change_source-handler-support/20160310-131140 > base: git://linuxtv.org/media_tree.git master > config: x86_64-rhel (attached as .config) > reproduce: > # save the attached .config to linux build tree > make ARCH=x86_6

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On 10/03/2016 16:26, Paolo Bonzini wrote: > Compared to smp_load_acquire(), smp_mb() adds an ordering between stores > and loads. Here, the ordering is load-store, hence... > The load of kvm->tlbs_dirty should then be > > /* >* Read tlbs_dirty before setting KVM_REQ_TLB_FLUSH in

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On 10/03/2016 16:26, Paolo Bonzini wrote: > Compared to smp_load_acquire(), smp_mb() adds an ordering between stores > and loads. Here, the ordering is load-store, hence... > The load of kvm->tlbs_dirty should then be > > /* >* Read tlbs_dirty before setting KVM_REQ_TLB_FLUSH in

Re: [PATCH 1/3] block: introduce device_add_disk()

On Thu, Mar 10, 2016 at 7:18 AM, Christoph Hellwig wrote: > On Thu, Mar 10, 2016 at 07:15:19AM -0800, Dan Williams wrote: >> > How are the callers expected to unwind after already having added the >> > disk? >> >> True, I overlooked making add_disk() unwind-able, will re-spin... > >

Re: [PATCH 1/3] block: introduce device_add_disk()

On Thu, Mar 10, 2016 at 7:18 AM, Christoph Hellwig wrote: > On Thu, Mar 10, 2016 at 07:15:19AM -0800, Dan Williams wrote: >> > How are the callers expected to unwind after already having added the >> > disk? >> >> True, I overlooked making add_disk() unwind-able, will re-spin... > > I think this

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On 10/03/2016 15:40, Xiao Guangrong wrote: > long dirty_count = kvm->tlbs_dirty; > > +/* > + * read tlbs_dirty before doing tlb flush to make sure not tlb > request is > + * lost. > + */ > smp_mb(); > + > if (kvm_make_all_cpus_request(kvm,

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On 10/03/2016 15:40, Xiao Guangrong wrote: > long dirty_count = kvm->tlbs_dirty; > > +/* > + * read tlbs_dirty before doing tlb flush to make sure not tlb > request is > + * lost. > + */ > smp_mb(); > + > if (kvm_make_all_cpus_request(kvm,

Re: [PATCH] avr32: fix asm operand constraint in cmpxchg()

On Thu, Mar 10, 2016 at 4:23 PM, Mans Rullgard wrote: > If the 'old' operand to cmpxchg() is a constant wider than 21 bits, > linking fails with a "relocation truncated to fit: R_AVR32_21S" error. > > Fix this by replacing the "i" constraint with "Ks21" which makes the > compiler

Re: [PATCH] avr32: fix asm operand constraint in cmpxchg()

On Thu, Mar 10, 2016 at 4:23 PM, Mans Rullgard wrote: > If the 'old' operand to cmpxchg() is a constant wider than 21 bits, > linking fails with a "relocation truncated to fit: R_AVR32_21S" error. > > Fix this by replacing the "i" constraint with "Ks21" which makes the > compiler use a temporary

Re: [PATCH v3 1/6] memory: omap-gpmc: Store handle to GPMC dev

On 03/10/2016 09:22 AM, Roger Quadros wrote: > Franklin, > > On 10/03/16 15:40, Franklin S Cooper Jr. wrote: >> >> On 03/10/2016 06:40 AM, Roger Quadros wrote: >>> Franklin, >>> >>> On 10/03/16 06:07, Franklin S Cooper Jr wrote: The dma channel information is located within the GPMC node.

Re: [PATCH v3 1/6] memory: omap-gpmc: Store handle to GPMC dev

On 03/10/2016 09:22 AM, Roger Quadros wrote: > Franklin, > > On 10/03/16 15:40, Franklin S Cooper Jr. wrote: >> >> On 03/10/2016 06:40 AM, Roger Quadros wrote: >>> Franklin, >>> >>> On 10/03/16 06:07, Franklin S Cooper Jr wrote: The dma channel information is located within the GPMC node.

Re: [PATCH v3 1/6] memory: omap-gpmc: Store handle to GPMC dev

Franklin, On 10/03/16 15:40, Franklin S Cooper Jr. wrote: > > > On 03/10/2016 06:40 AM, Roger Quadros wrote: >> Franklin, >> >> On 10/03/16 06:07, Franklin S Cooper Jr wrote: >>> The dma channel information is located within the GPMC node. The NAND >>> driver requires a handle to the GPMC's dev

Re: [PATCH v3 1/6] memory: omap-gpmc: Store handle to GPMC dev

Franklin, On 10/03/16 15:40, Franklin S Cooper Jr. wrote: > > > On 03/10/2016 06:40 AM, Roger Quadros wrote: >> Franklin, >> >> On 10/03/16 06:07, Franklin S Cooper Jr wrote: >>> The dma channel information is located within the GPMC node. The NAND >>> driver requires a handle to the GPMC's dev

Re: Got FPU related warning on Intel Quark during boot

On Thu, Mar 10, 2016 at 4:59 PM, Borislav Petkov wrote: > On Thu, Mar 10, 2016 at 03:31:43PM +0200, Andy Shevchenko wrote: >> Looks like it lacks that one. >> >> # grep -i fxsr /proc/cpuinfo; echo $? >> 1 > > Ok, so looking at where the warning comes from: > > [ 14.714533]

Re: Got FPU related warning on Intel Quark during boot

On Thu, Mar 10, 2016 at 4:59 PM, Borislav Petkov wrote: > On Thu, Mar 10, 2016 at 03:31:43PM +0200, Andy Shevchenko wrote: >> Looks like it lacks that one. >> >> # grep -i fxsr /proc/cpuinfo; echo $? >> 1 > > Ok, so looking at where the warning comes from: > > [ 14.714533] WARNING: CPU: 0 PID:

Re: [PATCH 1/3] block: introduce device_add_disk()

On Thu, Mar 10, 2016 at 12:09 AM, Christoph Hellwig wrote: >> /** >> - * add_disk - add partitioning information to kernel list >> + * device_add_disk - add partitioning information to kernel list >> + * @parent: parent device for the disk >> * @disk: per-device partitioning

Re: [PATCH 1/3] block: introduce device_add_disk()

On Thu, Mar 10, 2016 at 12:09 AM, Christoph Hellwig wrote: >> /** >> - * add_disk - add partitioning information to kernel list >> + * device_add_disk - add partitioning information to kernel list >> + * @parent: parent device for the disk >> * @disk: per-device partitioning information >> *

Re: [PATCH v3 16/19] x86, kaslr: Randomize physical and virtual address of kernel separately

On 03/09/16 at 10:07am, Kees Cook wrote: > On Wed, Mar 9, 2016 at 5:40 AM, Baoquan He wrote: > > On 03/08/16 at 10:24am, Kees Cook wrote: > >> On Mon, Mar 7, 2016 at 9:34 PM, Baoquan He wrote: > >> >> It seems like CONFIG_RANDOMIZE_BASE_MAX_OFFSET should have

Re: [PATCH v3 16/19] x86, kaslr: Randomize physical and virtual address of kernel separately

On 03/09/16 at 10:07am, Kees Cook wrote: > On Wed, Mar 9, 2016 at 5:40 AM, Baoquan He wrote: > > On 03/08/16 at 10:24am, Kees Cook wrote: > >> On Mon, Mar 7, 2016 at 9:34 PM, Baoquan He wrote: > >> >> It seems like CONFIG_RANDOMIZE_BASE_MAX_OFFSET should have been > >> >> eliminated when the

Re: [PATCH] serial-uartlite: fix build warning

> port->private_data = _le; > ^ > > Fixes: 2905697a82ea ("serial-uartlite: Constify uartlite_be/uartlite_le") > Signed-off-by: Sudip Mukherjee <sudip.mukher...@codethink.co.uk> > --- > > next-20160310 build log at: > https://travis-ci.org/sudipm

Re: Kernel docs: muddying the waters a bit

Em Thu, 10 Mar 2016 12:25:58 +0200 Jani Nikula escreveu: > TL;DR? Skip to the last paragraph. > > On Wed, 09 Mar 2016, Mauro Carvalho Chehab wrote: > > I guess the conversion to asciidoc format is now in good shape, > > at least to demonstrate

Re: [PATCH] serial-uartlite: fix build warning

> port->private_data = _le; > ^ > > Fixes: 2905697a82ea ("serial-uartlite: Constify uartlite_be/uartlite_le") > Signed-off-by: Sudip Mukherjee > --- > > next-20160310 build log at: > https://travis-ci.org/sudipm-mukherjee/parport/jobs/11498802

Re: Kernel docs: muddying the waters a bit

Em Thu, 10 Mar 2016 12:25:58 +0200 Jani Nikula escreveu: > TL;DR? Skip to the last paragraph. > > On Wed, 09 Mar 2016, Mauro Carvalho Chehab wrote: > > I guess the conversion to asciidoc format is now in good shape, > > at least to demonstrate that it is possible to use this format for the > >

Re: [PATCH 1/3] block: introduce device_add_disk()

On Thu, Mar 10, 2016 at 07:15:19AM -0800, Dan Williams wrote: > > How are the callers expected to unwind after already having added the > > disk? > > True, I overlooked making add_disk() unwind-able, will re-spin... I think this will take more work than we can finish in the next days. It would

Re: [PATCH 1/3] block: introduce device_add_disk()

On Thu, Mar 10, 2016 at 07:15:19AM -0800, Dan Williams wrote: > > How are the callers expected to unwind after already having added the > > disk? > > True, I overlooked making add_disk() unwind-able, will re-spin... I think this will take more work than we can finish in the next days. It would

Re: [PATCH] workqueue: warn if memory reclaim tries to flush !WQ_MEM_RECLAIM workqueue

On 03/12/15 21:26, Tejun Heo wrote: > Task or work item involved in memory reclaim trying to flush a > non-WQ_MEM_RECLAIM workqueue or one of its work items can lead to > deadlock. Trigger WARN_ONCE() if such conditions are detected. > > Signed-off-by: Tejun Heo > Cc: Peter

Re: [PATCH] workqueue: warn if memory reclaim tries to flush !WQ_MEM_RECLAIM workqueue

On 03/12/15 21:26, Tejun Heo wrote: > Task or work item involved in memory reclaim trying to flush a > non-WQ_MEM_RECLAIM workqueue or one of its work items can lead to > deadlock. Trigger WARN_ONCE() if such conditions are detected. > > Signed-off-by: Tejun Heo > Cc: Peter Zijlstra > --- >

[PATCH 1/1] hwmon: add support for Sensirion SHT3x sensors

From: David Frey This driver implements support for the Sensirion SHT3x-DIS chip, a humidity and temperature sensor. Temperature is measured in degrees Celsius, relative humidity is expressed as a percentage. In the sysfs interface, all values are scaled by 1000, i.e.

[PATCH 1/1] hwmon: add support for Sensirion SHT3x sensors

From: David Frey This driver implements support for the Sensirion SHT3x-DIS chip, a humidity and temperature sensor. Temperature is measured in degrees Celsius, relative humidity is expressed as a percentage. In the sysfs interface, all values are scaled by 1000, i.e. the value for 31.5 degrees

[PATCH 0/2] drivers/net/forcedeth: add support for WAKE_PHY

From: Karol Herbst I want to use my mac mini as a local server, but put it to sleep automatically therefore wol p, and because wol g is a mess if you want to wakeup the target machine automagically :) Karol Herbst (2): net/forcedeth: refactor wol support to make it

[PATCH 0/2] drivers/net/forcedeth: add support for WAKE_PHY

From: Karol Herbst I want to use my mac mini as a local server, but put it to sleep automatically therefore wol p, and because wol g is a mess if you want to wakeup the target machine automagically :) Karol Herbst (2): net/forcedeth: refactor wol support to make it easier adding more

[tip:irq/core] genirq: Export IRQ functions for module use

Commit-ID: 52b2a05fa7c8cfceebb59117a95decd68cf7e465 Gitweb: http://git.kernel.org/tip/52b2a05fa7c8cfceebb59117a95decd68cf7e465 Author: Quan Nguyen AuthorDate: Thu, 3 Mar 2016 21:56:52 +0700 Committer: Thomas Gleixner CommitDate: Thu, 10 Mar 2016

[tip:irq/core] genirq: Export IRQ functions for module use

Commit-ID: 52b2a05fa7c8cfceebb59117a95decd68cf7e465 Gitweb: http://git.kernel.org/tip/52b2a05fa7c8cfceebb59117a95decd68cf7e465 Author: Quan Nguyen AuthorDate: Thu, 3 Mar 2016 21:56:52 +0700 Committer: Thomas Gleixner CommitDate: Thu, 10 Mar 2016 16:00:35 +0100 genirq: Export IRQ

<    5   6   7   8   9   10   11   12   13   14   >