I'm back from travel and catching up. More info below.
eric
On 3/31/23 11:25, Igor Mammedov wrote:
On Wed, 29 Mar 2023 12:47:05 -0400
"Michael S. Tsirkin" wrote:
On Wed, Mar 29, 2023 at 08:14:37AM -0500, Eric DeVolder wrote:
On 3/29/23 00:19, Michael S. Tsirkin wrote:
Hmm I don't think w
On Wed, 29 Mar 2023 12:47:05 -0400
"Michael S. Tsirkin" wrote:
> On Wed, Mar 29, 2023 at 08:14:37AM -0500, Eric DeVolder wrote:
> >
> >
> > On 3/29/23 00:19, Michael S. Tsirkin wrote:
> > > Hmm I don't think we can reasonably make such a change for 8.0.
> > > Seems too risky.
> > > Also, I fe
On Thu, Mar 30, 2023 at 07:32:59PM +0530, Ani Sinha wrote:
>
>
> On Thu, 30 Mar 2023, Michael S. Tsirkin wrote:
>
> > On Thu, Mar 30, 2023 at 01:06:36PM +0530, Ani Sinha wrote:
> > >
> > >
> > > On Wed, 29 Mar 2023, Michael S. Tsirkin wrote:
> > >
> > > > On Wed, Mar 29, 2023 at 08:14:37AM -0500
On Thu, 30 Mar 2023, Michael S. Tsirkin wrote:
> On Thu, Mar 30, 2023 at 01:06:36PM +0530, Ani Sinha wrote:
> >
> >
> > On Wed, 29 Mar 2023, Michael S. Tsirkin wrote:
> >
> > > On Wed, Mar 29, 2023 at 08:14:37AM -0500, Eric DeVolder wrote:
> > > >
> > > >
> > > > On 3/29/23 00:19, Michael S. Ts
On Thu, Mar 30, 2023 at 01:06:36PM +0530, Ani Sinha wrote:
>
>
> On Wed, 29 Mar 2023, Michael S. Tsirkin wrote:
>
> > On Wed, Mar 29, 2023 at 08:14:37AM -0500, Eric DeVolder wrote:
> > >
> > >
> > > On 3/29/23 00:19, Michael S. Tsirkin wrote:
> > > > Hmm I don't think we can reasonably make such
On Wed, 29 Mar 2023, Michael S. Tsirkin wrote:
> On Wed, Mar 29, 2023 at 08:14:37AM -0500, Eric DeVolder wrote:
> >
> >
> > On 3/29/23 00:19, Michael S. Tsirkin wrote:
> > > Hmm I don't think we can reasonably make such a change for 8.0.
> > > Seems too risky.
> > > Also, I feel we want to have
On Wed, Mar 29, 2023 at 08:14:37AM -0500, Eric DeVolder wrote:
>
>
> On 3/29/23 00:19, Michael S. Tsirkin wrote:
> > Hmm I don't think we can reasonably make such a change for 8.0.
> > Seems too risky.
> > Also, I feel we want to have an internal (with "x-" prefix") flag to
> > revert to old beha
On 3/29/23 00:19, Michael S. Tsirkin wrote:
Hmm I don't think we can reasonably make such a change for 8.0.
Seems too risky.
Also, I feel we want to have an internal (with "x-" prefix") flag to
revert to old behaviour, in case of breakage on some guests. and maybe
we want to keep old revision
Hmm I don't think we can reasonably make such a change for 8.0.
Seems too risky.
Also, I feel we want to have an internal (with "x-" prefix") flag to
revert to old behaviour, in case of breakage on some guests. and maybe
we want to keep old revision for old machine types.
On Tue, Mar 28, 2023 at
I forgot to include the updated ACPI tables. I will do that as part of v2.
In the meantime, I appreciate any feedback...
eric
On 3/28/23 10:59, Eric DeVolder wrote:
The following Linux kernel change broke CPU hotplug for MADT revision
less than 5.
commit e2869bd7af60 ("x86/acpi/boot: Do not r
The following Linux kernel change broke CPU hotplug for MADT revision
less than 5.
commit e2869bd7af60 ("x86/acpi/boot: Do not register processors that cannot be
onlined for x2APIC")
As part of the investigation into resolving this breakage, I learned
that i386 QEMU reports revision 1, while te
11 matches
Mail list logo
