From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D513EC4361B for ; Wed, 16 Dec 2020 02:04:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9475A23102 for ; Wed, 16 Dec 2020 02:04:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725308AbgLPCEJ convert rfc822-to-8bit (ORCPT ); Tue, 15 Dec 2020 21:04:09 -0500 Received: from mail.kernel.org ([198.145.29.99]:39486 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725208AbgLPCEJ (ORCPT ); Tue, 15 Dec 2020 21:04:09 -0500 From: bugzilla-daemon@bugzilla.kernel.org Authentication-Results: mail.kernel.org; dkim=permerror (bad message/signature format) To: kvm@vger.kernel.org Subject: [Bug 210695] error: kvm run failed Invalid argument Date: Wed, 16 Dec 2020 02:03:28 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo virtualization_kvm@kernel-bugs.osdl.org X-Bugzilla-Product: Virtualization X-Bugzilla-Component: kvm X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: seanjc@google.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: virtualization_kvm@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=210695 Sean Christopherson (seanjc@google.com) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seanjc@google.com --- Comment #1 from Sean Christopherson (seanjc@google.com) --- Hrm, this is more than likely related to refactoring for the introduction of the TDP MMU. > kernel get_mmio_spte: detect reserved bits on spte, addr 0xfe013000, dump > hierarchy: > kernel ------ spte 0x80000b0e level 3. This SPTE looks odd/wrong, but unless I'm misreading things, there are no reserved bits set. > kernel ------ spte 0x49c0027 level 2. > kernel ------ spte 0x38001ffe0134d7 level 1. And this SPTE obviously has reserved bits set, but that's intentional and this should not trigger the warning as the SPTE should be recognized as an MMIO SPTE. I'll stare at this more tomorrow and play with things a bit to see if I can figure out what's broken. -- You are receiving this mail because: You are watching the assignee of the bug.