Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 62226C64ED6 for ; Tue, 28 Feb 2023 11:17:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231466AbjB1LR5 (ORCPT ); Tue, 28 Feb 2023 06:17:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38490 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229714AbjB1LRz (ORCPT ); Tue, 28 Feb 2023 06:17:55 -0500 Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 02CB1A9 for ; Tue, 28 Feb 2023 03:17:53 -0800 (PST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id B4BB8320093E for ; Tue, 28 Feb 2023 06:17:51 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Tue, 28 Feb 2023 06:17:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to; s=fm1; t=1677583071; x=1677669471; bh=yvjlCI3txL LE93Sd968GXY7YaAiAUE+clhRUl9XNwsE=; b=QMbniT5OkjYNcP13SWsIlGh/En OAwh5Tvv6Ouq0xVRB95x5n8nFA1orYkeSMrlTefEMxTz5Y8BgqJgBp1ODuXgV8rk 0RZnf/0SidWX/JTjsxCwqtwBFiehRSUSZAImE8Xnhnog+w4rUgL08Q4IUghbDx3b mWWqtoOYG3jieiTi2PdgWH5ZCj1vBpTFnxd/eUAiSrOYXABEusT+IdMc7GmqMPcT Zw4n/9QJHm3BTLFIhi8+v9VGRskFqkEMZJJDz6I2HYlSkibF1nNpnxsH7vztYRuG GH9W6+LJiRd4/BfFwieSM7hcbhB+AddxrDun6oLD5X0R53U4B/j4QqPAyHCw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1677583071; x=1677669471; bh=yvjlCI3txLLE93Sd968GXY7YaAiA UE+clhRUl9XNwsE=; b=Yx3nmqWoR5BTcD8u0cvvX8ywrVwYAo1uo3JoG39K34yr n3JYQPs8+dXeO2sKECNw8zkUCdaFKGBoW4Dt3og+Ksi7GKQW2vgbeWf9OOR5qQ9n IdIBPq0FIdNASjWBOSHJPpJRBi8K9S3eCrHQ7S96eR1d2JRwtncZV6Agj5hl6UXr csL9/pgZBrabZwU00za4a9Mu9XAvSesksMNdlmyHHaeZlG4l10EYtz90goW1ia+u 4CMXeMNTlHBQ3Etdf4aefH/+GC56zLfcnlsQtP88L7nzdGiQ0vNnHblDbl/QKCgb TuGYn8edTfvHZekAA06xSfYLM+AZ4oy9KVCK1PXkeg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudelvddgvdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkgggtgffothesthhqgh dtvddtjeenucfhrhhomhepoegsihhllhiisehfrghsthhmrghilhdrfhhmqeenucggtffr rghtthgvrhhnpeekgedvtdfhleeltedtkeefgfehiedtfedvudekkefgtdelveeuieffvd evvdfhgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhm pegsihhllhiisehfrghsthhmrghilhdrfhhm X-ME-Proxy: Feedback-ID: i8cf946af:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 28 Feb 2023 06:17:50 -0500 (EST) From: To: Subject: QUESTION: INT1 instruction for breakpoints Date: Tue, 28 Feb 2023 11:17:47 -0000 Message-ID: <000b01d94b66$4be1d8e0$e3a58aa0$@fastmail.fm> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdlLZWvw4Sfv0RpNQUyNFGreZ3AwPw== Content-Language: en-us Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org Is it possible to use the INT1 (instead of INT3) instruction for = breakpoints under KVM? It does not seem that this instruction causes a = KVM_EXIT_DEBUG (or any other exit) and it is silently skipped instead. If it is possible, how should I configure the KVM API to receive such = exits? Bill