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=-1.0 required=3.0 tests=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 21D86C3F2C6 for ; Sat, 29 Feb 2020 17:40:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D820F24677 for ; Sat, 29 Feb 2020 17:40:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727469AbgB2RkP convert rfc822-to-8bit (ORCPT ); Sat, 29 Feb 2020 12:40:15 -0500 Received: from mail.kernel.org ([198.145.29.99]:49240 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727349AbgB2RkO (ORCPT ); Sat, 29 Feb 2020 12:40:14 -0500 From: bugzilla-daemon@bugzilla.kernel.org To: kvm@vger.kernel.org Subject: [Bug 206579] KVM with passthrough generates "BUG: kernel NULL pointer dereference" and crashes Date: Sat, 29 Feb 2020 17:40:13 +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: rmuncrief@humanavance.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: 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 Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=206579 --- Comment #40 from muncrief (rmuncrief@humanavance.com) --- (In reply to Anthony from comment #39) > (In reply to muncrief from comment #38) > > (In reply to Anthony from comment #37) > ... Oh if that's the case then my understanding has just been poor as I assumed > the kvm_apicv_update_request counter should be higher to show the times > where apicv has been activated and deactivated which should also be > reflected in a trace. At least that is what it reads like to me reading this > patch - https://lore.kernel.org/patchwork/patch/1153605/ I took a look at that just out of curiosity Anthony but unfortunately I don't know anything about the Linux kernel code, I've just been following along with the devs as best I can. I'm simply a retired hardware/firmware/software designer from the olden days. And by "olden" I mean before Linux, and even things like CGA graphics, existed :) I was just passing along what I learned from Suravee, and some cursory observation of tiny related code segments. All I was ever able to accomplish was a partial understanding of the first 5 bits of the avic_inhibit_reasons output :) Your question is an interesting one though, I wasn't even aware that a request counter existed! -- You are receiving this mail because: You are watching the assignee of the bug.