On 09/12/2021, 14:53:31, Nathan Lynch wrote:
> Laurent Dufour writes:
>> On 08/12/2021, 16:21:29, Nathan Lynch wrote:
>>> Laurent Dufour writes:
On 07/12/2021, 18:07:50, Nathan Lynch wrote:
> Laurent Dufour writes:
>> On 07/12/2021, 15:32:39, Nathan Lynch wrote:
>>> Is there a r
Laurent Dufour writes:
> On 08/12/2021, 16:21:29, Nathan Lynch wrote:
>> Laurent Dufour writes:
>>> On 07/12/2021, 18:07:50, Nathan Lynch wrote:
Laurent Dufour writes:
> On 07/12/2021, 15:32:39, Nathan Lynch wrote:
>> Is there a reasonable fallback for VMs where this parameter doesn
On 08/12/2021, 16:21:29, Nathan Lynch wrote:
> Laurent Dufour writes:
>> On 07/12/2021, 18:07:50, Nathan Lynch wrote:
>>> Laurent Dufour writes:
On 07/12/2021, 15:32:39, Nathan Lynch wrote:
> Is there a reasonable fallback for VMs where this parameter doesn't
> exist? PowerVM partiti
Laurent Dufour writes:
> On 07/12/2021, 18:07:50, Nathan Lynch wrote:
>> Laurent Dufour writes:
>>> On 07/12/2021, 15:32:39, Nathan Lynch wrote:
Is there a reasonable fallback for VMs where this parameter doesn't
exist? PowerVM partitions should always have it, but what do we want the
>
On 07/12/2021, 18:18:40, Laurent Dufour wrote:
> On 07/12/2021, 18:07:50, Nathan Lynch wrote:
>> Laurent Dufour writes:
>>> On 07/12/2021, 15:32:39, Nathan Lynch wrote:
Is there a reasonable fallback for VMs where this parameter doesn't
exist? PowerVM partitions should always have it, bu
On 07/12/2021, 18:07:50, Nathan Lynch wrote:
> Laurent Dufour writes:
>> On 07/12/2021, 15:32:39, Nathan Lynch wrote:
>>> Is there a reasonable fallback for VMs where this parameter doesn't
>>> exist? PowerVM partitions should always have it, but what do we want the
>>> behavior to be on other hyp
Laurent Dufour writes:
> On 07/12/2021, 15:32:39, Nathan Lynch wrote:
>> Is there a reasonable fallback for VMs where this parameter doesn't
>> exist? PowerVM partitions should always have it, but what do we want the
>> behavior to be on other hypervisors?
>
> In that case, there is no value displ
On 07/12/2021, 15:32:39, Nathan Lynch wrote:
> Hi Laurent,
>
> Laurent Dufour writes:
>> +/*
>> + * PAPR defines, in section "7.3.16 System Parameters Option", the token 55
>> to
>> + * read the LPAR name.
>> + */
>> +#define SPLPAR_LPAR_NAME_TOKEN 55
>> +static void read_lpar_name(struct s
Hi Laurent,
Laurent Dufour writes:
> +/*
> + * PAPR defines, in section "7.3.16 System Parameters Option", the token 55
> to
> + * read the LPAR name.
> + */
> +#define SPLPAR_LPAR_NAME_TOKEN 55
> +static void read_lpar_name(struct seq_file *m)
> +{
> + int rc, len, token;
> + unio
The LPAR name may be changed after the LPAR has been started in the HMC.
In that case lparstat command is not reporting the updated value because it
reads it from the device tree which is read at boot time.
However this value could be read from RTAS.
Adding this value in the /proc/powerpc/lparcfg
10 matches
Mail list logo
