[PATCH 2/6] timekeeping: Use syscore_ops instead of sysdev class and sysdev

From: Rafael J. Wysocki The timekeeping subsystem uses a sysdev class and a sysdev for executing timekeeping_suspend() after interrupts have been turned off on the boot CPU (during system suspend) and for executing timekeeping_resume() before turning on interrupts on the boot CPU (during system

[PATCH 3/6] PCI / Intel IOMMU: Use syscore_ops instead of sysdev class and sysdev

From: Rafael J. Wysocki The Intel IOMMU subsystem uses a sysdev class and a sysdev for executing iommu_suspend() after interrupts have been turned off on the boot CPU (during system suspend) and for executing iommu_resume() before turning on interrupts on the boot CPU (during system resume

[PATCH 6/6] Introduce ARCH_NO_SYSDEV_OPS config option (v2)

From: Rafael J. Wysocki Introduce Kconfig option allowing architectures where sysdev operations used during system suspend, resume and shutdown have been completely replaced with struct sycore_ops operations to avoid building sysdev code that will never be used. Make callbacks in struct

[PATCH 5/6] cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)

From: Rafael J. Wysocki The cpufreq subsystem uses sysdev suspend and resume for executing cpufreq_suspend() and cpufreq_resume(), respectively, during system suspend, after interrupts have been switched off on the boot CPU, and during system resume, while interrupts are still off on the boot

[PATCH 4/6] KVM: Use syscore_ops instead of sysdev class and sysdev

From: Rafael J. Wysocki KVM uses a sysdev class and a sysdev for executing kvm_suspend() after interrupts have been turned off on the boot CPU (during system suspend) and for executing kvm_resume() before turning on interrupts on the boot CPU (during system resume). However, since both of these

[PATCH 1/6] x86: Use syscore_ops instead of sysdev classes and sysdevs

From: Rafael J. Wysocki Some subsystems in the x86 tree need to carry out suspend/resume and shutdown operations with one CPU on-line and interrupts disabled and they define sysdev classes and sysdevs or sysdev drivers for this purpose. This leads to unnecessarily complicated code and excessive

[PATCH 0/6] Do not use sysdevs for implementing "core" PM operations on x86

Hi, On Saturday, March 12, 2011, Rafael J. Wysocki wrote: > On Thursday, March 10, 2011, Rafael J. Wysocki wrote: > > There are multiple problems with sysdevs, or struct sys_device objects to > > be precise, that are so annoying that some people have started to think > > of r

Re: [PATCH 0/6] Do not use sysdevs for implementing "core" PM operations on x86

On Tuesday, March 22, 2011, Ingo Molnar wrote: > > * Rafael J. Wysocki wrote: > > > > If there are no objectsions, I'd like to push these patches through the > > > suspend > > > tree. > > > > [1/8] has been merged in the meantime and [3/8

Re: [PATCH 3/6] PCI / Intel IOMMU: Use syscore_ops instead of sysdev class and sysdev

On Tuesday, March 22, 2011, Joerg Roedel wrote: > On Mon, Mar 21, 2011 at 07:36:17PM -0400, Rafael J. Wysocki wrote: > > drivers/pci/intel-iommu.c | 38 +- > > 1 file changed, 9 insertions(+), 29 deletions(-) > > Looks good. May I take

[GIT PULL] More power management updates for 2.6.39

0 files changed, 206 insertions(+), 351 deletions(-) ----------- Rafael J. Wysocki (6): x86: Use syscore_ops instead of sysdev classes and sysdevs timekeeping: Use syscore_ops instead of sysdev class and sysdev PCI / Intel IOMMU: Use syscore_ops instead of sysdev class and s

Re: Linux Plumbers ACPI/PM, PCI Microconference

On Wednesday, July 17, 2013 08:31:55 AM Shuah Khan wrote: > Myron, > > On Tue, Jul 16, 2013 at 8:21 PM, Myron Stowe wrote: > > > > > Shuah - You brought up the idea about "Converting drivers from Legacy > > PM ops to dev_pm_ops"; would you like to present what you have > > done/encountered so fa

[Announcement] Linux Plumbers ACPI/PM, PCI Microconference

Hi All, The original announcement didn't go to linux-pm, so again: On Tuesday, July 16, 2013 08:21:26 PM Myron Stowe wrote: > Linux Plumbers has approved an ACPI/PM, PCI microconference. The > overview page is here: > > http://wiki.linuxplumbersconf.org/2013:pci_subsystem > > We would like to s

Re: [Announcement] Linux Plumbers ACPI/PM, PCI Microconference

On Wednesday, July 31, 2013 10:35:05 AM Shuah Khan wrote: > On Wed, Jul 31, 2013 at 5:40 AM, Rafael J. Wysocki wrote: > > Hi All, > > > > The original announcement didn't go to linux-pm, so again: > > > > On Tuesday, July 16, 2013 08:21:26 PM Myron Stowe wrot

Re: [PATCH] arm, kvm: fix double lock on cpu_add_remove_lock

nside > > kvm_arch_init() with holding cpu_add_remove_lock, so simply use > > __register_cpu_notifier() to fix the problem. > > > > Cc: Paolo Bonzini > > Cc: Christoffer Dall > > Cc: Srivatsa S. Bhat > > Cc: Rafael J. Wysocki > > Signed-off-by: Ming Lei &g

Re: [PATCH 15/15] Revert "x86: default to reboot via ACPI"

On Friday, 7 of November 2008, Robert Hancock wrote: > Matthew Garrett wrote: > > On Fri, Nov 07, 2008 at 09:01:19AM +0800, Zhao Yakui wrote: > > > >> With the help of KVM I find that the windows will be rebooted by writing > >> RESET_VALUE to RESET_REG I/O port if the RESET_REG_SUP bit is not > >

Re: 2.6.31.4 panic: CRED: put_cred_rcu() sees ffff880204e58c00 with usage 82150912

On Friday 30 October 2009, Nikola Ciprich wrote: > Ouch, typo in subject, it's 2.6.31.1 of course. sorry about that. > also CCing kvm. What about later kernels? Mainline in particular? Rafael -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@