From: Feng Li
In MC/S scenario, the conn->sess has been set NULL in
iscsi_login_non_zero_tsih_s1 when the second connection comes here,
then kernel panic.
The conn->sess will be assigned in iscsi_login_non_zero_tsih_s2. So
we should check whether it's NULL before calling.
From: Feng Li
In MC/S scenario, the conn->sess has been set NULL in
iscsi_login_non_zero_tsih_s1 when the second connection comes here,
then kernel panic.
The conn->sess will be assigned in iscsi_login_non_zero_tsih_s2. So
we should check whether it's NULL before calling.
Signed-off-by: Feng
On 11/07/2016 15:48, Radim Krčmář wrote:
>>> I guess the easiest solution is to replace kvm_apic_id with a field in
>>> struct kvm_lapic, which is already shifted right by 24 in xAPIC mode.
>
> (I guess the fewest LOC is to look at vcpu->vcpu_id, which is equal to
> x2apic id. xapic id cannot
Mesh HWMP module will be able to rely on the HW
RC algorithm if it exists, for path metric calculations.
This allows the metric calculation mechanism to calculate
a correct metric, based on PER and last TX rate both via
HW RC algorithm if it exists or via parameters collected
by the SW.
On 09/07/16 03:09, Mitchel Humpherys wrote:
> From: Jeremy Gebben
>
> Allow the creation of privileged mode mappings, for stage 1 only.
>
> Signed-off-by: Jeremy Gebben
> ---
> drivers/iommu/io-pgtable-arm.c | 16 +++-
> 1 file
On 11/07/2016 15:48, Radim Krčmář wrote:
>>> I guess the easiest solution is to replace kvm_apic_id with a field in
>>> struct kvm_lapic, which is already shifted right by 24 in xAPIC mode.
>
> (I guess the fewest LOC is to look at vcpu->vcpu_id, which is equal to
> x2apic id. xapic id cannot
Mesh HWMP module will be able to rely on the HW
RC algorithm if it exists, for path metric calculations.
This allows the metric calculation mechanism to calculate
a correct metric, based on PER and last TX rate both via
HW RC algorithm if it exists or via parameters collected
by the SW.
On 09/07/16 03:09, Mitchel Humpherys wrote:
> From: Jeremy Gebben
>
> Allow the creation of privileged mode mappings, for stage 1 only.
>
> Signed-off-by: Jeremy Gebben
> ---
> drivers/iommu/io-pgtable-arm.c | 16 +++-
> 1 file changed, 11 insertions(+), 5 deletions(-)
>
> diff
Dropped the XXX comment (oops),
moved the current_has_pending_bios() helper to bio.h
and dropped the identical ones from bio.c and md.h.
Reposted in-thread as
[PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
Thanks,
Lars Ellenberg
On Thu, Jul 07, 2016 at 12:35:02PM -0600, Stephen Warren wrote:
> On 07/07/2016 12:13 PM, Sivaram Nair wrote:
> >On Tue, Jul 05, 2016 at 05:04:22PM +0800, Joseph Lo wrote:
> >>Add DT binding for the Hardware Synchronization Primitives (HSP). The
> >>HSP is designed for the processors to share
Dropped the XXX comment (oops),
moved the current_has_pending_bios() helper to bio.h
and dropped the identical ones from bio.c and md.h.
Reposted in-thread as
[PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
Thanks,
Lars Ellenberg
On Thu, Jul 07, 2016 at 12:35:02PM -0600, Stephen Warren wrote:
> On 07/07/2016 12:13 PM, Sivaram Nair wrote:
> >On Tue, Jul 05, 2016 at 05:04:22PM +0800, Joseph Lo wrote:
> >>Add DT binding for the Hardware Synchronization Primitives (HSP). The
> >>HSP is designed for the processors to share
On 11 July 2016 at 13:31, Vinay Simha wrote:
> emil,
>
> As you had suggested to drop the spurious returns in
> jdi_panel_unprepare and drop the return itself.
> But as i had mentioned earlier , we cannot drop the return function
> and void for jdi_panel_unprepare , since the
On 11 July 2016 at 13:31, Vinay Simha wrote:
> emil,
>
> As you had suggested to drop the spurious returns in
> jdi_panel_unprepare and drop the return itself.
> But as i had mentioned earlier , we cannot drop the return function
> and void for jdi_panel_unprepare , since the drm fun* requires
On Mon, Jul 11, 2016 at 03:17:01PM +0800, Antoine, Peter wrote:
>Do you have the firmware package for the SKL huc?
Sorry, no, is this error log due to lack of the firmware?
Thanks,
Xiaolong
>
>Peter
>-Original Message-
>From: lkp-requ...@eclists.intel.com
On Mon, Jul 11, 2016 at 03:17:01PM +0800, Antoine, Peter wrote:
>Do you have the firmware package for the SKL huc?
Sorry, no, is this error log due to lack of the firmware?
Thanks,
Xiaolong
>
>Peter
>-Original Message-
>From: lkp-requ...@eclists.intel.com
For a long time, generic_make_request() converts recursion into
iteration by queuing recursive arguments on current->bio_list.
This is convenient for stacking drivers,
the top-most driver would take the originally submitted bio,
and re-submit a re-mapped version of it, or one or more clones,
or
For a long time, generic_make_request() converts recursion into
iteration by queuing recursive arguments on current->bio_list.
This is convenient for stacking drivers,
the top-most driver would take the originally submitted bio,
and re-submit a re-mapped version of it, or one or more clones,
or
On Mon, 11 Jul 2016, Anna-Maria Gleixner wrote:
> @@ -5896,7 +5877,7 @@ void kvm_arch_exit(void)
> if (!boot_cpu_has(X86_FEATURE_CONSTANT_TSC))
> cpufreq_unregister_notifier(_cpufreq_notifier_block,
> CPUFREQ_TRANSITION_NOTIFIER);
> -
On Mon, 11 Jul 2016, Anna-Maria Gleixner wrote:
> @@ -5896,7 +5877,7 @@ void kvm_arch_exit(void)
> if (!boot_cpu_has(X86_FEATURE_CONSTANT_TSC))
> cpufreq_unregister_notifier(_cpufreq_notifier_block,
> CPUFREQ_TRANSITION_NOTIFIER);
> -
On 09/07/16 03:09, Mitchel Humpherys wrote:
> Add the IOMMU_PRIV attribute, which is used to indicate privileged
> mappings.
>
> Signed-off-by: Mitchel Humpherys
> ---
> include/linux/iommu.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On 09/07/16 03:09, Mitchel Humpherys wrote:
> Add the IOMMU_PRIV attribute, which is used to indicate privileged
> mappings.
>
> Signed-off-by: Mitchel Humpherys
> ---
> include/linux/iommu.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/iommu.h b/include/linux/iommu.h
From: Jiri Kosina
Convert the per-device linked list into a hashtable. The primary
motivation for this change is that currently, we're not tracking all the
qdiscs in hierarchy (e.g. excluding default qdiscs), as the lookup
performed over the linked list by
On Mon, 27 Jun 2016, Torsten Duwe wrote:
> diff --git a/arch/arm64/include/asm/livepatch.h
> b/arch/arm64/include/asm/livepatch.h
> new file mode 100644
> index 000..6b9a3d1
> --- /dev/null
> +++ b/arch/arm64/include/asm/livepatch.h
> @@ -0,0 +1,37 @@
> +/*
> + * livepatch.h - arm64-specific
From: Jiri Kosina
Convert the per-device linked list into a hashtable. The primary
motivation for this change is that currently, we're not tracking all the
qdiscs in hierarchy (e.g. excluding default qdiscs), as the lookup
performed over the linked list by qdisc_match_from_root() is rather
On Mon, 27 Jun 2016, Torsten Duwe wrote:
> diff --git a/arch/arm64/include/asm/livepatch.h
> b/arch/arm64/include/asm/livepatch.h
> new file mode 100644
> index 000..6b9a3d1
> --- /dev/null
> +++ b/arch/arm64/include/asm/livepatch.h
> @@ -0,0 +1,37 @@
> +/*
> + * livepatch.h - arm64-specific
On Mon, Jul 04, 2016 at 01:46:39AM +0900, Yoshinori Sato wrote:
> Signed-off-by: Yoshinori Sato
> ---
> .../interrupt-controller/iodata-landisk.txt| 31 ++
> drivers/irqchip/Makefile | 2 +-
> drivers/irqchip/irq-io-landisk.c
On Mon, Jul 04, 2016 at 01:46:39AM +0900, Yoshinori Sato wrote:
> Signed-off-by: Yoshinori Sato
> ---
> .../interrupt-controller/iodata-landisk.txt| 31 ++
> drivers/irqchip/Makefile | 2 +-
> drivers/irqchip/irq-io-landisk.c | 72
>
Hey Mitch,
Thanks for having the necessary go at the DMA API - I think the series
looks broadly workable now.
On 09/07/16 03:09, Mitchel Humpherys wrote:
> The following patch to the ARM SMMU driver:
>
> commit d346180e70b91b3d5a1ae7e5603e65593d4622bc
> Author: Robin Murphy
Hey Mitch,
Thanks for having the necessary go at the DMA API - I think the series
looks broadly workable now.
On 09/07/16 03:09, Mitchel Humpherys wrote:
> The following patch to the ARM SMMU driver:
>
> commit d346180e70b91b3d5a1ae7e5603e65593d4622bc
> Author: Robin Murphy
> Date:
On Fri, Jul 01, 2016 at 03:45:30PM +0800, Shawn Lin wrote:
> This patch adds description for no-sd, no-sdio, no-mmc. We
> expect the specific boards adds these in DT to improve
> the initialization. For instance, for a soldered eMMC slot,
> we could skip sending SDIO and SD commands to probe its
On Fri, Jul 01, 2016 at 03:45:30PM +0800, Shawn Lin wrote:
> This patch adds description for no-sd, no-sdio, no-mmc. We
> expect the specific boards adds these in DT to improve
> the initialization. For instance, for a soldered eMMC slot,
> we could skip sending SDIO and SD commands to probe its
On Mon, Jul 11, 2016 at 09:40:04AM -0400, Vivek Goyal wrote:
On Sat, Jul 09, 2016 at 01:41:38AM +0800, kbuild test robot wrote:
Hi,
[auto build test ERROR on next-20160708]
[also build test ERROR on v4.7-rc6]
[cannot apply to pcmoore-selinux/next security/next v4.7-rc6 v4.7-rc5 v4.7-rc4]
[if
On Mon, Jul 11, 2016 at 09:40:04AM -0400, Vivek Goyal wrote:
On Sat, Jul 09, 2016 at 01:41:38AM +0800, kbuild test robot wrote:
Hi,
[auto build test ERROR on next-20160708]
[also build test ERROR on v4.7-rc6]
[cannot apply to pcmoore-selinux/next security/next v4.7-rc6 v4.7-rc5 v4.7-rc4]
[if
2016-07-11 18:14+0800, Yang Zhang:
> On 2016/7/11 15:43, Paolo Bonzini wrote:
>> On 11/07/2016 08:07, Yang Zhang wrote:
>> > >
>> > > mutex_lock(>arch.apic_map_lock);
>> > >
>> > > +kvm_for_each_vcpu(i, vcpu, kvm)
>> > > +if (kvm_apic_present(vcpu))
>> > > +max_id =
2016-07-11 18:14+0800, Yang Zhang:
> On 2016/7/11 15:43, Paolo Bonzini wrote:
>> On 11/07/2016 08:07, Yang Zhang wrote:
>> > >
>> > > mutex_lock(>arch.apic_map_lock);
>> > >
>> > > +kvm_for_each_vcpu(i, vcpu, kvm)
>> > > +if (kvm_apic_present(vcpu))
>> > > +max_id =
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.hotplug
head: 0e5de16e9e45b4d853a31761fd74ff56998169a1
commit: 19d18a28764b80cd2e451c1ab85f12b090d2a875 [31/66] x86/kvm/kvmclock:
Convert to hotplug state machine
config: x86_64-allyesconfig (attached as .config)
compiler:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.hotplug
head: 0e5de16e9e45b4d853a31761fd74ff56998169a1
commit: 19d18a28764b80cd2e451c1ab85f12b090d2a875 [31/66] x86/kvm/kvmclock:
Convert to hotplug state machine
config: x86_64-allyesconfig (attached as .config)
compiler:
On Mon, Jul 11 2016 at 9:27am -0400,
Matthias Dahl wrote:
> Hello Mike...
>
> On 2016-07-11 15:18, Mike Snitzer wrote:
>
> >Something must explain the execessive nature of your leak but
> >it isn't a known issue.
>
> Since I am currently setting up the new
On Mon, Jul 11 2016 at 9:27am -0400,
Matthias Dahl wrote:
> Hello Mike...
>
> On 2016-07-11 15:18, Mike Snitzer wrote:
>
> >Something must explain the execessive nature of your leak but
> >it isn't a known issue.
>
> Since I am currently setting up the new machine, all tests were
> performed
Port the xattr functionality to the new xattr_handler API.
This is smallest changes needed to move to this new API. The
function ll_removexattr can be replaced by generic_removexattr
as well since it also uses the xattr_handler set xattr backend.
To tell the difference between the two cases we
Port the xattr functionality to the new xattr_handler API.
This is smallest changes needed to move to this new API. The
function ll_removexattr can be replaced by generic_removexattr
as well since it also uses the xattr_handler set xattr backend.
To tell the difference between the two cases we
On Sat, Jul 09, 2016 at 01:41:38AM +0800, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on next-20160708]
> [also build test ERROR on v4.7-rc6]
> [cannot apply to pcmoore-selinux/next security/next v4.7-rc6 v4.7-rc5
> v4.7-rc4]
> [if your patch is applied to the wrong git tree,
On Sat, Jul 09, 2016 at 01:41:38AM +0800, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on next-20160708]
> [also build test ERROR on v4.7-rc6]
> [cannot apply to pcmoore-selinux/next security/next v4.7-rc6 v4.7-rc5
> v4.7-rc4]
> [if your patch is applied to the wrong git tree,
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
Topi-Miettinen/capabilities-audit-capability-use/20160711-191824
commit c24bf954b59269134ee89584ca466fafd5e98c38 ("capabilities: audit
capability use")
in testcase: boot
on test machine: 1 threads qemu-sys
FYI, we noticed the following commit:
https://github.com/0day-ci/linux
Topi-Miettinen/capabilities-audit-capability-use/20160711-191824
commit c24bf954b59269134ee89584ca466fafd5e98c38 ("capabilities: audit
capability use")
in testcase: boot
on test machine: 1 threads qemu-sys
Inlining reply below after thinking further.
On Mon, Jul 11 2016 at 9:18am -0400,
Mike Snitzer wrote:
> On Mon, Jul 11 2016 at 4:31am -0400,
> Matthias Dahl wrote:
>
> > Hello,
> >
> > I made a few more tests and here my observations:
>
Inlining reply below after thinking further.
On Mon, Jul 11 2016 at 9:18am -0400,
Mike Snitzer wrote:
> On Mon, Jul 11 2016 at 4:31am -0400,
> Matthias Dahl wrote:
>
> > Hello,
> >
> > I made a few more tests and here my observations:
> >
> > - kernels 4.4.8 and 4.5.5 show the same
On Mon, Jul 11, 2016 at 06:12:30PM +0800, Xishi Qiu wrote:
> Hi,
>
> We can use mprotect to set read only or read/write.
>
> mprotect_fixup()
> vma_set_page_prot()
> vm_pgprot_modify()
> vm_get_page_prot()
>
On Mon, Jul 11, 2016 at 06:12:30PM +0800, Xishi Qiu wrote:
> Hi,
>
> We can use mprotect to set read only or read/write.
>
> mprotect_fixup()
> vma_set_page_prot()
> vm_pgprot_modify()
> vm_get_page_prot()
>
On Tue, Jul 5, 2016 at 4:59 PM, Jeff Layton wrote:
> On Thu, 2016-06-30 at 15:47 +0200, Andreas Gruenbacher wrote:
>> A richacl roughly grants a requested access if the NFSv4 acl in the
>> richacl grants the requested permissions according to the NFSv4
>> permission check
On Tue, Jul 5, 2016 at 4:59 PM, Jeff Layton wrote:
> On Thu, 2016-06-30 at 15:47 +0200, Andreas Gruenbacher wrote:
>> A richacl roughly grants a requested access if the NFSv4 acl in the
>> richacl grants the requested permissions according to the NFSv4
>> permission check algorithm and the file
Hello Mike...
On 2016-07-11 15:18, Mike Snitzer wrote:
Something must explain the execessive nature of your leak but
it isn't a known issue.
Since I am currently setting up the new machine, all tests were
performed w/ various live cd images (Fedora Rawhide, Gentoo, ...)
and I saw the exact
Hello Mike...
On 2016-07-11 15:18, Mike Snitzer wrote:
Something must explain the execessive nature of your leak but
it isn't a known issue.
Since I am currently setting up the new machine, all tests were
performed w/ various live cd images (Fedora Rawhide, Gentoo, ...)
and I saw the exact
On Tue, Jul 5, 2016 at 3:39 PM, Jeff Layton wrote:
> On Thu, 2016-06-30 at 15:46 +0200, Andreas Gruenbacher wrote:
>> We need to map from POSIX permissions to NFSv4 permissions when a
>> chmod() is done, from NFSv4 permissions to POSIX permissions when an acl
>> is set (which
On Tue, Jul 5, 2016 at 3:39 PM, Jeff Layton wrote:
> On Thu, 2016-06-30 at 15:46 +0200, Andreas Gruenbacher wrote:
>> We need to map from POSIX permissions to NFSv4 permissions when a
>> chmod() is done, from NFSv4 permissions to POSIX permissions when an acl
>> is set (which implicitly sets the
From: Yu-cheng Yu
When the kernel is using XSAVES compacted format, we cannot do
__copy_from_user() from a signal frame, which has standard-format data.
Fix it by using copyin_to_xsaves(), which converts between formats and
filters out all supervisor states that we do not
On Mon, Jul 11 2016 at 4:31am -0400,
Matthias Dahl wrote:
> Hello,
>
> I made a few more tests and here my observations:
>
> - kernels 4.4.8 and 4.5.5 show the same behavior
>
> - the moment dd starts, memory usage spikes rapidly and within a just
> a few
From: Yu-cheng Yu
It is an error to request a disabled XSAVE/XSAVES component address.
For that case, make __raw_xsave_addr() return a NULL and issue a
warning.
Signed-off-by: Yu-cheng Yu
Signed-off-by: Fenghua Yu
From: Yu-cheng Yu
When the kernel is using XSAVES compacted format, we cannot do
__copy_from_user() from a signal frame, which has standard-format data.
Fix it by using copyin_to_xsaves(), which converts between formats and
filters out all supervisor states that we do not allow userspace to
On Mon, Jul 11 2016 at 4:31am -0400,
Matthias Dahl wrote:
> Hello,
>
> I made a few more tests and here my observations:
>
> - kernels 4.4.8 and 4.5.5 show the same behavior
>
> - the moment dd starts, memory usage spikes rapidly and within a just
> a few seconds has filled up all 32 GiB
From: Yu-cheng Yu
It is an error to request a disabled XSAVE/XSAVES component address.
For that case, make __raw_xsave_addr() return a NULL and issue a
warning.
Signed-off-by: Yu-cheng Yu
Signed-off-by: Fenghua Yu
Reviewed-by: Dave Hansen
---
arch/x86/kernel/fpu/xstate.c | 5 +
1 file
On 07/08/2016 05:41 PM, Andrew Morton wrote:
On Wed, 6 Jul 2016 17:42:36 -0400 Jason Baron wrote:
Although dynamic debug is often only used for debug builds, sometimes its
enabled for production builds as well. Minimize its impact by using jump
labels. This reduces the
On 07/08/2016 05:41 PM, Andrew Morton wrote:
On Wed, 6 Jul 2016 17:42:36 -0400 Jason Baron wrote:
Although dynamic debug is often only used for debug builds, sometimes its
enabled for production builds as well. Minimize its impact by using jump
labels. This reduces the text section by 7000+
From: Yu-cheng Yu
** Based on tip/master **
This is Part 3 of previous 13 XSAVES patches. Break it down to
smaller series. There are no code changes; only minor fixes in
the titles.
Yu-cheng Yu (4):
x86/fpu/xstate: Fix __fpu_restore_sig() for XSAVES
x86/fpu/xstate:
From: Yu-cheng Yu
** Based on tip/master **
This is Part 3 of previous 13 XSAVES patches. Break it down to
smaller series. There are no code changes; only minor fixes in
the titles.
Yu-cheng Yu (4):
x86/fpu/xstate: Fix __fpu_restore_sig() for XSAVES
x86/fpu/xstate: Return NULL for disabled
From: Yu-cheng Yu
We did not handle XSAVES instructions correctly. There were issues in
converting between standard and compacted format when interfacing with
user-space. These issues have been corrected.
Add a WARN_ONCE() to make it clear that XSAVES supervisor states
From: Yu-cheng Yu
In XSAVES mode if fpstate_init() is used to initialize a
task's extended state area, xsave.header.xcomp_bv[63] must
be set. Otherwise, when the task is scheduled, a warning is
triggered from copy_kernel_to_xregs().
One such test case is: setting an
From: Yu-cheng Yu
We did not handle XSAVES instructions correctly. There were issues in
converting between standard and compacted format when interfacing with
user-space. These issues have been corrected.
Add a WARN_ONCE() to make it clear that XSAVES supervisor states are not
yet implemented.
From: Yu-cheng Yu
In XSAVES mode if fpstate_init() is used to initialize a
task's extended state area, xsave.header.xcomp_bv[63] must
be set. Otherwise, when the task is scheduled, a warning is
triggered from copy_kernel_to_xregs().
One such test case is: setting an invalid extended state
On 11/07/16 10:56, James Liao wrote:
[...]
@@ -467,28 +386,54 @@ static int scpsys_probe(struct platform_device *pdev)
if (PTR_ERR(scpd->supply) == -ENODEV)
scpd->supply = NULL;
else
-
On 11/07/16 10:56, James Liao wrote:
[...]
@@ -467,28 +386,54 @@ static int scpsys_probe(struct platform_device *pdev)
if (PTR_ERR(scpd->supply) == -ENODEV)
scpd->supply = NULL;
else
-
From: Konstantin Neumoin
The balloon has a special mechanism that is subscribed to the oom
notification which leads to deflation for a fixed number of pages.
The number is always fixed even when the balloon is fully deflated.
But leak_balloon did not expect that the pages
From: Konstantin Neumoin
The balloon has a special mechanism that is subscribed to the oom
notification which leads to deflation for a fixed number of pages.
The number is always fixed even when the balloon is fully deflated.
But leak_balloon did not expect that the pages to deflate will be more
A usb device in the connection state. Then host is suspend and resume.
But the usb device could not be at the right speed. We should be reset
the reset.
Signed-off-by: Pengcheng Li
---
drivers/usb/core/hub.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff
A usb device in the connection state. Then host is suspend and resume.
But the usb device could not be at the right speed. We should be reset
the reset.
Signed-off-by: Pengcheng Li
---
drivers/usb/core/hub.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
On Monday, July 11, 2016 03:29:55 PM Stephen Rothwell wrote:
> Hi Mika,
>
> On Mon, 11 Jul 2016 07:48:17 +0300 Mika Westerberg
> wrote:
> >
> > Looks like it is the module name (configfs.o) that confuses modpost or
> > linker. The below patch fixes it for me.
>
On Monday, July 11, 2016 03:29:55 PM Stephen Rothwell wrote:
> Hi Mika,
>
> On Mon, 11 Jul 2016 07:48:17 +0300 Mika Westerberg
> wrote:
> >
> > Looks like it is the module name (configfs.o) that confuses modpost or
> > linker. The below patch fixes it for me.
>
> That makes sense. Thanks.
On Mon, Jul 11, 2016 at 07:03:31AM -0400, Jeff Layton wrote:
> On Mon, 2016-07-11 at 09:23 +0200, Michal Hocko wrote:
> > On Fri 08-07-16 10:27:38, Jeff Layton wrote:
> > > On Fri, 2016-07-08 at 16:23 +0200, Michal Hocko wrote:
> > > > On Fri 08-07-16 08:51:54, Jeff Layton wrote:
> > > > >
> > >
On Mon, Jul 11, 2016 at 07:03:31AM -0400, Jeff Layton wrote:
> On Mon, 2016-07-11 at 09:23 +0200, Michal Hocko wrote:
> > On Fri 08-07-16 10:27:38, Jeff Layton wrote:
> > > On Fri, 2016-07-08 at 16:23 +0200, Michal Hocko wrote:
> > > > On Fri 08-07-16 08:51:54, Jeff Layton wrote:
> > > > >
> > >
More or less straightforward, although this driver sports some very
interesting SMP setup code. Regarding the callback ordering, this
deleted comment is interesting:
... the GIC needs to be up before the ARM generic timers.
That comment is half baken as the same requirement is true for perf.
More or less straightforward, although this driver sports some very
interesting SMP setup code. Regarding the callback ordering, this
deleted comment is interesting:
... the GIC needs to be up before the ARM generic timers.
That comment is half baken as the same requirement is true for perf.
From: Sebastian Andrzej Siewior
Install the callbacks via the state machine and let the core invoke
the callbacks on the already online CPUs.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Andy Lutomirski
Cc: x...@kernel.org
From: Richard Cochran
Install the callbacks via the state machine.
Signed-off-by: Richard Cochran
Reviewed-by: Sebastian Andrzej Siewior
Cc: Jason Cooper
Cc: Marc Zyngier
From: Richard Cochran
Install the callbacks via the state machine.
Signed-off-by: Richard Cochran
Reviewed-by: Sebastian Andrzej Siewior
Cc: Jason Cooper
Cc: Marc Zyngier
Signed-off-by: Anna-Maria Gleixner
---
drivers/irqchip/irq-gic-v3.c | 22 +++---
From: Sebastian Andrzej Siewior
Install the callbacks via the state machine and let the core invoke
the callbacks on the already online CPUs.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Andy Lutomirski
Cc: x...@kernel.org
Signed-off-by: Anna-Maria Gleixner
---
arch/x86/entry/vdso/vma.c |
From: Richard Cochran
Install the callbacks via the state machine and let the core invoke
the callbacks on the already online CPUs.
Signed-off-by: Richard Cochran
Reviewed-by: Sebastian Andrzej Siewior
Cc: Jason Cooper
From: Richard Cochran
Install the callbacks via the state machine.
Signed-off-by: Richard Cochran
Cc: Jason Cooper
Cc: Marc Zyngier
Signed-off-by: Anna-Maria Gleixner
---
From: Richard Cochran
Install the callbacks via the state machine and let the core invoke
the callbacks on the already online CPUs.
Signed-off-by: Richard Cochran
Reviewed-by: Sebastian Andrzej Siewior
Cc: Jason Cooper
Cc: Marc Zyngier
Signed-off-by: Anna-Maria Gleixner
---
From: Richard Cochran
Install the callbacks via the state machine.
Signed-off-by: Richard Cochran
Cc: Jason Cooper
Cc: Marc Zyngier
Signed-off-by: Anna-Maria Gleixner
---
drivers/irqchip/irq-armada-370-xp.c | 44
include/linux/cpuhotplug.h |
From: Sebastian Andrzej Siewior
Install the callbacks via the state machine.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Andrew Lunn
Cc: Gregory Clement
Cc: Sebastian Hesselbarth
From: Thomas Gleixner
Replace the perf_notifier() install mechanism, which invokes magically
the callback on the current CPU. Convert the hardware specific
callbacks which are invoked from the x86 perf core to return proper
error codes instead of totally pointless NOTIFY_BAD
From: Sebastian Andrzej Siewior
Install the callbacks via the state machine.
Signed-off-by: Sebastian Andrzej Siewior
Cc: Andrew Lunn
Cc: Gregory Clement
Cc: Sebastian Hesselbarth
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Anna-Maria Gleixner
---
From: Thomas Gleixner
Replace the perf_notifier() install mechanism, which invokes magically
the callback on the current CPU. Convert the hardware specific
callbacks which are invoked from the x86 perf core to return proper
error codes instead of totally pointless NOTIFY_BAD return values.
From: Thomas Gleixner
Actually a nice symmetric startup/teardown pair which fits proper in
the state machine concept. In the long run we should be able to invoke
the startup callback for the boot CPU via the state machine and get
rid of the init function which invokes it on
From: Thomas Gleixner
Actually a nice symmetric startup/teardown pair which fits proper in
the state machine concept. In the long run we should be able to invoke
the startup callback for the boot CPU via the state machine and get
rid of the init function which invokes it on the boot CPU.
Note:
From: Richard Cochran
Install the callbacks via the state machine and let the core invoke
the callbacks on the already online CPUs.
Signed-off-by: Richard Cochran
Reviewed-by: Sebastian Andrzej Siewior
Signed-off-by:
From: Thomas Gleixner
Convert the notifiers to state machine states and let the core code do the
setup for the already online CPUs. This notifier has a completely undocumented
ordering requirement versus perf hardcoded in the notifier priority. This
odering is only required
From: Richard Cochran
Install the callbacks via the state machine and let the core invoke
the callbacks on the already online CPUs.
Signed-off-by: Richard Cochran
Reviewed-by: Sebastian Andrzej Siewior
Signed-off-by: Anna-Maria Gleixner
---
arch/x86/events/intel/rapl.c | 84
From: Thomas Gleixner
Convert the notifiers to state machine states and let the core code do the
setup for the already online CPUs. This notifier has a completely undocumented
ordering requirement versus perf hardcoded in the notifier priority. This
odering is only required for cpu down, so that
901 - 1000 of 1694 matches
Mail list logo