Anthony Liguori wrote:
Glauber Costa wrote:
Anthony Liguori wrote:
No, it can't. Because at the time qemu starts, no vcpu - thread id
relationship exists at all. And we don't know when it will.
Sure we do. The vcpu - thread id relationship is valid after
kvm_init_ap() is called which
Avi Kivity wrote:
Glauber Costa wrote:
Hi guys,
Here's a first series of patch aiming at vcpu pinning support in qemu.
Ideally, as vcpu as just normal threads, the usual userspace tools can
be used
to set cpu affinities mask.
However, It makes it very difficult to _start_ a vm with vcpus
Avi Kivity wrote:
Affinity control is probably useful mostly for numa configurations,
where you want to restrict virtual cpus to run on the cores closest to
memory. However it may well be that the scheduler is already good
enough to do this on its own.
In that case, you need to use
Hi guys,
Here's a first series of patch aiming at vcpu pinning support in qemu.
Ideally, as vcpu as just normal threads, the usual userspace tools can be used
to set cpu affinities mask.
However, It makes it very difficult to _start_ a vm with vcpus pinned, since
we don't know the thread ids
Glauber Costa wrote:
Hi guys,
Here's a first series of patch aiming at vcpu pinning support in qemu.
Ideally, as vcpu as just normal threads, the usual userspace tools can be used
to set cpu affinities mask.
However, It makes it very difficult to _start_ a vm with vcpus pinned, since
we
Anthony Liguori wrote:
Glauber Costa wrote:
Hi guys,
Here's a first series of patch aiming at vcpu pinning support in qemu.
Ideally, as vcpu as just normal threads, the usual userspace tools can
be used
to set cpu affinities mask.
However, It makes it very difficult to _start_ a vm with
Joerg Roedel wrote:
On Tue, Mar 04, 2008 at 01:21:53PM -0300, Glauber Costa wrote:
Hi guys,
Here's a first series of patch aiming at vcpu pinning support in qemu.
Ideally, as vcpu as just normal threads, the usual userspace tools can be
used
to set cpu affinities mask.
However, It makes
On Tue, Mar 04, 2008 at 03:11:27PM -0300, Glauber Costa wrote:
Joerg Roedel wrote:
On Tue, Mar 04, 2008 at 01:21:53PM -0300, Glauber Costa wrote:
Hi guys,
Here's a first series of patch aiming at vcpu pinning support in qemu.
Ideally, as vcpu as just normal threads, the usual userspace
Glauber Costa wrote:
My main interest is in management tools being able to specify pinning
set ups at VM creation time.
As I said, it can be done through tools like taskset, but then you'd
have to know:
* when are the threads created
* which thread ids corresponds to each cpu
And of
On Tue, Mar 04, 2008 at 01:28:24PM -0600, Anthony Liguori wrote:
Glauber Costa wrote:
My main interest is in management tools being able to specify pinning
set ups at VM creation time.
As I said, it can be done through tools like taskset, but then you'd
have to know:
* when are the
Daniel P. Berrange wrote:
On Tue, Mar 04, 2008 at 01:28:24PM -0600, Anthony Liguori wrote:
Glauber Costa wrote:
My main interest is in management tools being able to specify pinning
set ups at VM creation time.
As I said, it can be done through tools like taskset, but then you'd
have to
Anthony Liguori wrote:
Glauber Costa wrote:
My main interest is in management tools being able to specify pinning
set ups at VM creation time.
As I said, it can be done through tools like taskset, but then you'd
have to know:
* when are the threads created
* which thread ids corresponds
Glauber Costa wrote:
Anthony Liguori wrote:
No, it can't. Because at the time qemu starts, no vcpu - thread id
relationship exists at all. And we don't know when it will.
Sure we do. The vcpu - thread id relationship is valid after
kvm_init_ap() is called which is after machine init but
Glauber Costa wrote:
Hi guys,
Here's a first series of patch aiming at vcpu pinning support in qemu.
Ideally, as vcpu as just normal threads, the usual userspace tools can be used
to set cpu affinities mask.
However, It makes it very difficult to _start_ a vm with vcpus pinned, since
we
Anthony Liguori wrote:
Glauber Costa wrote:
Anthony Liguori wrote:
No, it can't. Because at the time qemu starts, no vcpu - thread id
relationship exists at all. And we don't know when it will.
Sure we do. The vcpu - thread id relationship is valid after
kvm_init_ap() is
Anthony Liguori wrote:
Glauber Costa wrote:
My main interest is in management tools being able to specify pinning
set ups at VM creation time.
As I said, it can be done through tools like taskset, but then you'd
have to know:
* when are the threads created
* which thread ids corresponds
16 matches
Mail list logo
