On 1/18/23 16:17, Kevin Wolf wrote:
Am 18.01.2023 um 11:53 hat Thomas Huth geschrieben:
On 17/01/2023 14.31, Nina Schoetterl-Glausch wrote:
On Tue, 2023-01-17 at 08:30 +0100, Thomas Huth wrote:
On 16/01/2023 22.09, Nina Schoetterl-Glausch wrote:
On Thu, 2023-01-05 at 15:53 +0100, Pierre
Am 18.01.2023 um 11:53 hat Thomas Huth geschrieben:
> On 17/01/2023 14.31, Nina Schoetterl-Glausch wrote:
> > On Tue, 2023-01-17 at 08:30 +0100, Thomas Huth wrote:
> > > On 16/01/2023 22.09, Nina Schoetterl-Glausch wrote:
> > > > On Thu, 2023-01-05 at 15:53 +0100, Pierre Morel wrote:
> > > > > The
On 1/11/23 11:09, Thomas Huth wrote:
On 05/01/2023 15.53, Pierre Morel wrote:
The modification of the CPU attributes are done through a monitor
commands.
s/commands/command/
thx
It allows to move the core inside the topology tree to optimise
the cache usage in the case the host's
On 1/18/23 11:53, Thomas Huth wrote:
On 17/01/2023 14.31, Nina Schoetterl-Glausch wrote:
On Tue, 2023-01-17 at 08:30 +0100, Thomas Huth wrote:
On 16/01/2023 22.09, Nina Schoetterl-Glausch wrote:
On Thu, 2023-01-05 at 15:53 +0100, Pierre Morel wrote:
The modification of the CPU attributes
On 1/16/23 22:09, Nina Schoetterl-Glausch wrote:
On Thu, 2023-01-05 at 15:53 +0100, Pierre Morel wrote:
The modification of the CPU attributes are done through a monitor
commands.
It allows to move the core inside the topology tree to optimise
the cache usage in the case the host's
On 1/12/23 13:03, Daniel P. Berrangé wrote:
On Thu, Jan 05, 2023 at 03:53:10PM +0100, Pierre Morel wrote:
The modification of the CPU attributes are done through a monitor
commands.
It allows to move the core inside the topology tree to optimise
the cache usage in the case the host's
On 17/01/2023 14.31, Nina Schoetterl-Glausch wrote:
On Tue, 2023-01-17 at 08:30 +0100, Thomas Huth wrote:
On 16/01/2023 22.09, Nina Schoetterl-Glausch wrote:
On Thu, 2023-01-05 at 15:53 +0100, Pierre Morel wrote:
The modification of the CPU attributes are done through a monitor
commands.
It
On Tue, 2023-01-17 at 08:30 +0100, Thomas Huth wrote:
> On 16/01/2023 22.09, Nina Schoetterl-Glausch wrote:
> > On Thu, 2023-01-05 at 15:53 +0100, Pierre Morel wrote:
> > > The modification of the CPU attributes are done through a monitor
> > > commands.
> > >
> > > It allows to move the core
On 16/01/2023 22.09, Nina Schoetterl-Glausch wrote:
On Thu, 2023-01-05 at 15:53 +0100, Pierre Morel wrote:
The modification of the CPU attributes are done through a monitor
commands.
It allows to move the core inside the topology tree to optimise
the cache usage in the case the host's
On Thu, 2023-01-05 at 15:53 +0100, Pierre Morel wrote:
> The modification of the CPU attributes are done through a monitor
> commands.
>
> It allows to move the core inside the topology tree to optimise
> the cache usage in the case the host's hypervizor previously
> moved the CPU.
>
> The same
On Thu, Jan 05, 2023 at 03:53:10PM +0100, Pierre Morel wrote:
> The modification of the CPU attributes are done through a monitor
> commands.
>
> It allows to move the core inside the topology tree to optimise
> the cache usage in the case the host's hypervizor previously
> moved the CPU.
>
>
On 11/01/2023 11.09, Thomas Huth wrote:
On 05/01/2023 15.53, Pierre Morel wrote:
The modification of the CPU attributes are done through a monitor
commands.
s/commands/command/
It allows to move the core inside the topology tree to optimise
the cache usage in the case the host's hypervizor
On 05/01/2023 15.53, Pierre Morel wrote:
The modification of the CPU attributes are done through a monitor
commands.
s/commands/command/
It allows to move the core inside the topology tree to optimise
the cache usage in the case the host's hypervizor previously
s/hypervizor/hypervisor/
The modification of the CPU attributes are done through a monitor
commands.
It allows to move the core inside the topology tree to optimise
the cache usage in the case the host's hypervizor previously
moved the CPU.
The same command allows to modifiy the CPU attributes modifiers
like
14 matches
Mail list logo
