On Fri, 21 Feb 2025 16:23:07 -0500, Hamza Mahfooz wrote:
>On Fri, Feb 21, 2025 at 11:23:28AM +0900, Ryo Takakura wrote:
>> On Thu, 20 Feb 2025 17:53:00 -0500, Hamza Mahfooz wrote:
>> >Since, the panic handlers may require certain cpus to be online to panic
>> >gracefully, we should call them before
On Fri, Feb 21, 2025 at 11:56:32AM -0800, Nuno Das Neves wrote:
> Running in the root partition is a unique and specialized case that
> requires additional code. CONFIG_MSHV_ROOT allows Hyper-V guest kernels
> to exclude this code, which is important since significant additional code
> specific to
From: Hamza Mahfooz Sent: Friday, February
21, 2025 1:31 PM
>
> Since, the panic handlers may require certain cpus to be online to panic
> gracefully, we should call them before turning off SMP. Without this
> re-ordering, on Hyper-V hv_panic_vmbus_unload() times out, because the
> vmbus channel
On 2/21/2025 12:58 PM, Michael Kelley wrote:
> From: Nuno Das Neves Sent: Friday,
> February 21, 2025 11:57 AM
>>
>> Introduce hv_curr_partition_type to store the partition type
>> as an enum.
>>
>> Right now this is limited to guest or root partition, but there will
>> be other kinds in future a
Hey Ryo,
On Fri, Feb 21, 2025 at 11:23:28AM +0900, Ryo Takakura wrote:
> Hi Hamza!
>
> On Thu, 20 Feb 2025 17:53:00 -0500, Hamza Mahfooz wrote:
> >Since, the panic handlers may require certain cpus to be online to panic
> >gracefully, we should call them before turning off SMP. Without this
> >re
Since, the panic handlers may require certain cpus to be online to panic
gracefully, we should call them before turning off SMP. Without this
re-ordering, on Hyper-V hv_panic_vmbus_unload() times out, because the
vmbus channel is bound to VMBUS_CONNECT_CPU and unless the crashing cpu
is the same as
On 2/21/2025 12:01 PM, Nuno Das Neves wrote:
> The subject line says v2 but this is actually v3!
>
> Nuno
For the series,
Reviewed-by: Easwar Hariharan
From: Nuno Das Neves Sent: Friday, February
21, 2025 11:57 AM
>
> CONFIG_MSHV_ROOT allows kernels built to run as a normal Hyper-V guest
> to exclude the root partition code, which is expected to grow
> significantly over time.
>
> This option is a tristate so future driver code can be built as
From: Nuno Das Neves Sent: Friday, February
21, 2025 11:57 AM
>
> Introduce hv_curr_partition_type to store the partition type
> as an enum.
>
> Right now this is limited to guest or root partition, but there will
> be other kinds in future and the enum is easily extensible.
>
> Set up hv_curr
The subject line says v2 but this is actually v3!
Nuno
On 2/21/2025 11:56 AM, Nuno Das Neves wrote:
> Running in the root partition is a unique and specialized case that
> requires additional code. CONFIG_MSHV_ROOT allows Hyper-V guest kernels
> to exclude this code, which is important since sign
Introduce hv_curr_partition_type to store the partition type
as an enum.
Right now this is limited to guest or root partition, but there will
be other kinds in future and the enum is easily extensible.
Set up hv_curr_partition_type early in Hyper-V initialization with
hv_identify_partition_type()
Running in the root partition is a unique and specialized case that
requires additional code. CONFIG_MSHV_ROOT allows Hyper-V guest kernels
to exclude this code, which is important since significant additional code
specific to the root partition is expected to be added over time.
To do this, chang
CONFIG_MSHV_ROOT allows kernels built to run as a normal Hyper-V guest
to exclude the root partition code, which is expected to grow
significantly over time.
This option is a tristate so future driver code can be built as a
(m)odule, allowing faster development iteration cycles.
If CONFIG_MSHV_RO
Return linux-friendly error codes from hypercall helper functions,
which allows them to be used more flexibly.
Introduce hv_result_to_errno() for this purpose, which also handles
the special value U64_MAX returned from hv_do_hypercall().
Signed-off-by: Nuno Das Neves
Reviewed-by: Easwar Harihara
On Fri, Feb 21, 2025 at 12:09:57AM +0900, Krzysztof Wilczyński wrote:
> Hello,
>
> > > The VF driver controls an endpoint attached to the pci-hyperv
> > > controller. An invalidation sent by the PF driver in the host would be
> > > delivered *to* the endpoint driver by the controller driver.
> > >
On 2/21/25 10:10, Nuno Das Neves wrote:
> On 2/20/2025 2:59 PM, MUKESH RATHOR wrote:
>>
>>
>> On 2/20/25 14:56, Easwar Hariharan wrote:
>> > On 2/20/2025 1:59 PM, MUKESH RATHOR wrote:
>> >>
>> >>
>> >> On 2/20/25 10:33, Nuno Das Neves wrote:
>> >> > Introduce hv_current_parti
On 2/21/2025 10:10 AM, Nuno Das Neves wrote:
> On 2/20/2025 2:59 PM, MUKESH RATHOR wrote:
>>
>>
>> On 2/20/25 14:56, Easwar Hariharan wrote:
>> > On 2/20/2025 1:59 PM, MUKESH RATHOR wrote:
>> >>
>> >>
>> >> On 2/20/25 10:33, Nuno Das Neves wrote:
>> >> > Introduce hv_current_partition_type t
On 2/20/2025 2:59 PM, MUKESH RATHOR wrote:
>
>
> On 2/20/25 14:56, Easwar Hariharan wrote:
> > On 2/20/2025 1:59 PM, MUKESH RATHOR wrote:
> >>
> >>
> >> On 2/20/25 10:33, Nuno Das Neves wrote:
> >> > Introduce hv_current_partition_type to store the partition type
> >> > as an enum.
> >
* Roman Kisel wrote:
> Roman Kisel (2):
> x86/hyperv: VTL mode emergency restart callback
> x86/hyperv: VTL mode callback for restarting the system
A: These two patch titles verbs.
...
...
B: These two patch titles are missing verbs.
Like me you prefer B too, right? If so, please add back
19 matches
Mail list logo
