Searched hist:"36 da91bd" (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/arch/x86/kvm/ |
H A D | i8254.h | 36da91bd Wed Oct 19 06:50:47 CDT 2016 Petr Mladek <pmladek@suse.com> KVM: x86: Handle the kthread worker using the new API
Use the new API to create and destroy the "kvm-pit" kthread worker. The API hides some implementation details.
In particular, kthread_create_worker() allocates and initializes struct kthread_worker. It runs the kthread the right way and stores task_struct into the worker structure.
kthread_destroy_worker() flushes all pending works, stops the kthread and frees the structure.
This patch does not change the existing behavior except for dynamically allocating struct kthread_worker and storing only the pointer of this structure.
It is compile tested only because I did not find an easy way how to run the code. Well, it should be pretty safe given the nature of the change.
Signed-off-by: Petr Mladek <pmladek@suse.com> Message-Id: <1476877847-11217-1-git-send-email-pmladek@suse.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> 36da91bd Wed Oct 19 06:50:47 CDT 2016 Petr Mladek <pmladek@suse.com> KVM: x86: Handle the kthread worker using the new API Use the new API to create and destroy the "kvm-pit" kthread worker. The API hides some implementation details. In particular, kthread_create_worker() allocates and initializes struct kthread_worker. It runs the kthread the right way and stores task_struct into the worker structure. kthread_destroy_worker() flushes all pending works, stops the kthread and frees the structure. This patch does not change the existing behavior except for dynamically allocating struct kthread_worker and storing only the pointer of this structure. It is compile tested only because I did not find an easy way how to run the code. Well, it should be pretty safe given the nature of the change. Signed-off-by: Petr Mladek <pmladek@suse.com> Message-Id: <1476877847-11217-1-git-send-email-pmladek@suse.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|
H A D | i8254.c | 36da91bd Wed Oct 19 06:50:47 CDT 2016 Petr Mladek <pmladek@suse.com> KVM: x86: Handle the kthread worker using the new API
Use the new API to create and destroy the "kvm-pit" kthread worker. The API hides some implementation details.
In particular, kthread_create_worker() allocates and initializes struct kthread_worker. It runs the kthread the right way and stores task_struct into the worker structure.
kthread_destroy_worker() flushes all pending works, stops the kthread and frees the structure.
This patch does not change the existing behavior except for dynamically allocating struct kthread_worker and storing only the pointer of this structure.
It is compile tested only because I did not find an easy way how to run the code. Well, it should be pretty safe given the nature of the change.
Signed-off-by: Petr Mladek <pmladek@suse.com> Message-Id: <1476877847-11217-1-git-send-email-pmladek@suse.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> 36da91bd Wed Oct 19 06:50:47 CDT 2016 Petr Mladek <pmladek@suse.com> KVM: x86: Handle the kthread worker using the new API Use the new API to create and destroy the "kvm-pit" kthread worker. The API hides some implementation details. In particular, kthread_create_worker() allocates and initializes struct kthread_worker. It runs the kthread the right way and stores task_struct into the worker structure. kthread_destroy_worker() flushes all pending works, stops the kthread and frees the structure. This patch does not change the existing behavior except for dynamically allocating struct kthread_worker and storing only the pointer of this structure. It is compile tested only because I did not find an easy way how to run the code. Well, it should be pretty safe given the nature of the change. Signed-off-by: Petr Mladek <pmladek@suse.com> Message-Id: <1476877847-11217-1-git-send-email-pmladek@suse.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|