[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [BUG] x2apic broken with current AMD hardware


  • To: Elliott Mitchell <ehem+xen@xxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Wed, 8 Mar 2023 16:50:51 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=lVJTkEd2Am/7yZ4M/sSjafvc77TzID74PbmD8WXNn+s=; b=GBCBx9MxJltba6s0jGIGFGJbx2Tqz9Ikek9nvfMsQd0zAJ1i1EMYy77anBkyUWVh11/XBEDCld2LVZboIzpboz9VxLB+XbU0g3hY0etgwJhw0NUucupbYyGUS02M1ZqswmggUf6w2Sr6/NXegLRo/yrqkrzpSnuxnZTlfmuihvAsfs1qDIeiuyHFKDFozYHgCgFWUQ35UujR+AZzUkXkYVqZSn9Mma2w/pWzneqZmwdrA2cc0QY0ts6Lhdkfe2MK2Y/U9XQ9CS6FG6taRVy+I9VTNdiKx0D5b+BnGMoi4lmAp6Jn94F3NgUtKpIu0toKYNOgGyk09twmesB9NMTx5w==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZDCmaFl5ACfft+lXtDmjUTja2uGDqrdOPFbYIVLsQwJcC62QrnBI61fJ2SviUkrkf8AX8wxj5UBqr8ff2mj18KRrEpLoY5enJhWI5HpaXw8UTFqyGLSWBPzyohDRXR4PL5vLAtgbOgo/QESFoUzjzA33miSVmfWpjFyUuGE9BwHwJx/eK21oUr6QEY6KWpEXHysC4TOtvSa8lWUVDT6gkTjDartgaAm97IA3LuW5g9Q1AcAeWhK4/FsDs6ILCsncRIyXQKQRhggsbB9oJp5+O1KI91eDvX1Uu9s9LUsQ1Mvj45BMO5opifpf32TLvJhbxz0GZ3aatLf5MVWGXU7bzA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 08 Mar 2023 15:51:05 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 08.03.2023 16:23, Elliott Mitchell wrote:
> Mostly SSIA.  As originally identified by "Neowutran", appears Xen's
> x2apic wrapper implementation fails with current generation AMD hardware
> (Ryzen 7xxx/Zen 4).  This can be worked around by passing "x2apic=false"
> on Xen's command-line, though I'm wondering about the performance impact.
> 
> There hasn't been much activity on xen-devel WRT x2apic, so a patch which
> fixed this may have flown under the radar.  Most testing has also been
> somewhat removed from HEAD.
> 
> Thanks to "Neowutran" for falling on this grenade and making it easier
> for the followers.  Pointer to first report:
> https://forum.qubes-os.org/t/ryzen-7000-serie/14538

I'm sorry, but when you point at this long a report, would you please be a
little more specific as to where the problem in question is actually
mentioned? Searching the page for "x2apic" didn't give any hits at all
until I first scrolled to the bottom of the (at present) 95 comments. And
then while there are five mentions, there's nothing I could spot that
would actually help understanding what is actually wrong. A statement like
"... is because the implementation of x2apic is incorrect" isn't helpful
on its own. And a later statement by another person puts under question
whether "x2apic=false" actually helps in all cases.

Please can we get a proper bug report here with suitable technical detail?
Or alternatively a patch to discuss?

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.