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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 45C0AEB64DD for ; Mon, 24 Jul 2023 19:37:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230295AbjGXThn (ORCPT ); Mon, 24 Jul 2023 15:37:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42216 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229541AbjGXThl (ORCPT ); Mon, 24 Jul 2023 15:37:41 -0400 Received: from mail-yw1-x114a.google.com (mail-yw1-x114a.google.com [IPv6:2607:f8b0:4864:20::114a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A37B51B3 for ; Mon, 24 Jul 2023 12:37:39 -0700 (PDT) Received: by mail-yw1-x114a.google.com with SMTP id 00721157ae682-573cacf4804so60234257b3.1 for ; Mon, 24 Jul 2023 12:37:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1690227459; x=1690832259; h=cc:to:from:subject:message-id:mime-version:date:reply-to:from:to:cc :subject:date:message-id:reply-to; bh=O4VWgPiua4ZmSDkThmKhRK2lyYjlOypYwlqtCHhU3qo=; b=F/34vdGPJzVdninBmHaaYps8MkTJYqcn8LiDiws1Gv9uty0wqqclSdi5PAck/jLSQ8 EcvJd0MXjWq+ozQp31NWYaFd+VTGDlut71Qqrqv/Qg4H1ujvRnubTaajPpFNnoBweu0M oD4S1+sp8BqCqEuaH6IQAGP81DI3GAPBZhuBKv0CoLbXzC/z+R+Wd2Ag72X9NzgeOl5Q lMXjB8hE6JbU6/PZRlXHvU7xkq9MdpO9Csy+OLjbBwzxy5pLFWwNIK9tfQ46O3+mDDnZ ABbVfHKJBmLVtKzHA1Fe/rCU4NvdrZ6ogNs+M3yzlpLaPX+2qfVUk9U1m5xDOTr3BasY 3dsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690227459; x=1690832259; h=cc:to:from:subject:message-id:mime-version:date:reply-to :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=O4VWgPiua4ZmSDkThmKhRK2lyYjlOypYwlqtCHhU3qo=; b=cjounjF9sNbHGoPCyuZxbenjnQXLFCdxdDEiOHhnesbM68cPgT4UoBhLEBAAgDBBxt jEaWPN64p/PWAo6sDhajDJKcQz0DgOpUUVVNJspn1RtdGnqlB1YD0X2DDLqOT81HYq8j emydPu3sfrY2ktxgLSmbg7Jyjkk2JRgJGqPJhAE+9mg9b73dkNVpxFAoKE869JNHLjhH ssY/m6i/Ni9UMGG1G8NV2FsKuZCERt0MMigpZMyefBKg+r2nmm2XjJUEBrgsasLyruDv Wg1+9d3l/a+PVpTu9UqA6eleT5l3ej2OtjjFY5GFARsawN1PuTyBRvk6PxzwUTsXeB6N ROkQ== X-Gm-Message-State: ABy/qLasaU8uLShkjStp0aBwGDoUnI2lvhR1ige+sgGi2UnjcpN1ckVk WVMoo1qp5TF8WdEZRVxcZHvNRrdiK4Y= X-Google-Smtp-Source: APBJJlG4XX11fRNdTWxSIJ1x78nNmOIsCxonkuectk9GCCLaduDufbvEPsVji3+TYABpm1rQkYjd/u9/tRY= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a81:ae54:0:b0:576:6e4e:b87f with SMTP id g20-20020a81ae54000000b005766e4eb87fmr73392ywk.10.1690227458870; Mon, 24 Jul 2023 12:37:38 -0700 (PDT) Reply-To: Sean Christopherson Date: Mon, 24 Jul 2023 12:37:00 -0700 Mime-Version: 1.0 X-Mailer: git-send-email 2.41.0.487.g6d72f3e995-goog Message-ID: <20230724193700.54825-1-seanjc@google.com> Subject: [ANNOUNCE / CFP] KVM Microconference at LPC 2023 From: Sean Christopherson To: Sean Christopherson Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Paolo Bonzini Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We are excited to announce the first KVM MC at Plumbers 2023! The KVM microconference will focus on KVM itself, as well as KVM's touchpoints with other kernel subsystems. The purpose of the KVM MC is to supplement KVM Forum by providing developers with a dedicated vehicle for discussing kernel internals. Topics that are primarily aimed at something other than KVM are firmly out of scope and will be rejected. Please consider the Confidential Computing MC, the VFIO/IOMMU/PCI MC, or KVM Forum 2024 for virtualization topics that aren't directly related to KVM internals. The KVM MC will be comprised of ~3 "big" topics, and ~6 (+/-2) "small" topics. Big topics will be allotted 30-40 minutes, and small topics 10-20 minutes. Please add a note in your submission if you would like your topic to be considered for a big slot (consider it a hint to help us rough in the scedule). Below is a list of *ideas* for topics. Topics that are not on the list are more than welcome! If we were omniscient, we wouldn't need this CFP! Note, priority will be given to open problems, i.e. things that have already been posted/discussed on LKML, but posting before LPC is NOT a hard requirement. Potential Topics: - Serving inaccessible/unmappable memory for KVM guests (a.k.a. guest_memfd) - Optimizing mmu_notifiers, e.g. reducing TLB flushes and spurious zapping - Supporting multiple KVM modules (for non-disruptive upgrades) - Improving and hardening KVM+perf interactions - Implementing arch-agnostic abstractions in KVM (e.g. MMU) - Defining KVM requirements for hardware vendors - Utilizing "fault" injection to increase test coverage of edge cases - KVM vs VFIO (e.g. memory types, a rather hot topic on the ARM side) Abstracts can be submitted via https://lpc.events/event/17/abstracts. Don't forget to select "KVM MC" as the track! Thanks!