From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id unoLCo+s9WGhMwAAWB0awg (envelope-from ) for ; Sat, 29 Jan 2022 16:07:27 -0500 Received: by simark.ca (Postfix, from userid 112) id 111AE1F3B4; Sat, 29 Jan 2022 16:07:27 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 7BDCC1EA69 for ; Sat, 29 Jan 2022 16:07:26 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 97B6A385843F for ; Sat, 29 Jan 2022 21:07:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 97B6A385843F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1643490445; bh=U3dc3xqDLlTpC2E+9rOE/F5axFiCJUonmG/KQjDXwZ0=; h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=bxCrsgFkVCCoPImjNo4IpBIXW/7yPgOWpJSgh7KJ1DTkWErbO3p/2L/1QWYJn3U72 FmOD/U9wTnGKUsHQxDaD/ZnLZnMs7iKdqJuQG2bZgLlQ8CfWZiwKG5PdqT5TuOt5gP hyBz8A7VgfwYghr56wmdRcvzX3VOAPqE8rQ7wKKM= Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by sourceware.org (Postfix) with ESMTPS id C68DD3858D28 for ; Sat, 29 Jan 2022 21:07:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C68DD3858D28 Received: by mail-yb1-xb2a.google.com with SMTP id c19so12231ybf.2 for ; Sat, 29 Jan 2022 13:07:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=U3dc3xqDLlTpC2E+9rOE/F5axFiCJUonmG/KQjDXwZ0=; b=SBtFomk71TydMhpK2J71xY+ySMIHy5k9dShhmqlQ9U9sncM3XTqjWogcanJKH+Khkn kGzxJm6NXZYdGFElKz4FWZviNAvscWPCXEt6r7cneyH658rLqEIkZ7m7DXBczF/w7i0B Tq00PcJb8kaMg0WLQGy6XUxaoNX5MX5AO2Y2LjcrddiOCuSUX8UMk5a8ejHAxa4Al7dy jVyBNRzFdpIO0wYaGrduW31aCmHzK88TKD80SgJGI9wqJHffBXNQqIa+s7jD/1qeU70q yB2td/qo0npgjs5V/NWi+pwswVVayXeJqbCwMqJkWqWHHNdDewkeUEVZIzkuU4/pa/hW snKA== X-Gm-Message-State: AOAM530hpnpPeWzJkElQoUQBkTZldThDq50olN6CwD1IWt06UvNK1It7 qzP6O2zsbYI6959V1Ep0zk5+Dtd4ML2dCBJR4jgQL/g7JF0Ptg== X-Google-Smtp-Source: ABdhPJwsHFOowFI71uk77bu4yu1OCDa0mZHuTMX6PJrsJxa/x+zhRVKNQoXRn0d9zL3p2ISMTvZD6GeHERES792aGTs= X-Received: by 2002:a25:7c3:: with SMTP id 186mr21870996ybh.235.1643490420350; Sat, 29 Jan 2022 13:07:00 -0800 (PST) MIME-Version: 1.0 Date: Sat, 29 Jan 2022 23:06:48 +0200 Message-ID: Subject: gdb switches to __sysvec_apic_timer_interrupt or __default_send_IPI_dest_field with KVM enabled To: qemu-discuss@nongnu.org, linux-kernel@vger.kernel.org, gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Vasyl Vavrychuk via Gdb Reply-To: Vasyl Vavrychuk Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hello, I run Linux kernel under qemu-system-x86_64 via the "-kernel" option. Also, I added the "-s" option to accept the gdb connection. After Linux boot up I connect with gdb and set a breakpoint in some function, for example "device_del", does not matter really. The problem is if I also use "--enable-kvm", then after breakpoint triggered and sending "n" from gdb, it switches to __sysvec_apic_timer_interrupt (regs=0xffffc90000297de8) at arch/x86/kernel/apic/apic.c:1102 1102 trace_local_timer_entry(LOCAL_TIMER_VECTOR); or to __default_send_IPI_dest_field (mask=, vector=, dest=dest@entry=2048) at arch/x86/kernel/apic/ipi.c:161 161 cfg = __prepare_ICR2(mask); I am stepping over kernel code that does not perform any waiting or blocking. Everything works fine with "--enable-kvm" removed. Thanks, Vasyl