qemu-riscv.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
	alistair.francis@wdc.com,  bmeng@tinylab.org,
	liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
	 palmer@rivosinc.com, ajones@ventanamicro.com
Subject: Re: [PATCH 0/2] target/riscv/kvm: update KVM exts to Linux 6.8
Date: Wed, 6 Mar 2024 12:53:13 +1000	[thread overview]
Message-ID: <CAKmqyKMvbLheLiExSgKQEykc7XAgSLw+TZsoKU=etJmi0nkAMw@mail.gmail.com> (raw)
In-Reply-To: <20240304134732.386590-1-dbarboza@ventanamicro.com>

On Mon, Mar 4, 2024 at 11:48 PM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> Let's update QEMU KVM extension support up to 6.8-rc6 before the 9.0
> freeze.
>
> Patches based on alistair/riscv-to-apply.next.
>
> Daniel Henrique Barboza (2):
>   linux-headers: Update to Linux v6.8-rc6
>   target/riscv/kvm: update KVM exts to Linux 6.8

Thanks!

Applied to riscv-to-apply.next

Alistair

>
>  include/standard-headers/drm/drm_fourcc.h     |  10 +-
>  include/standard-headers/linux/ethtool.h      |  41 +++--
>  .../standard-headers/linux/virtio_config.h    |   8 +-
>  include/standard-headers/linux/virtio_pci.h   |  68 +++++++++
>  include/standard-headers/linux/virtio_pmem.h  |   7 +
>  linux-headers/asm-generic/unistd.h            |  15 +-
>  linux-headers/asm-mips/mman.h                 |   2 +-
>  linux-headers/asm-mips/unistd_n32.h           |   5 +
>  linux-headers/asm-mips/unistd_n64.h           |   5 +
>  linux-headers/asm-mips/unistd_o32.h           |   5 +
>  linux-headers/asm-powerpc/unistd_32.h         |   5 +
>  linux-headers/asm-powerpc/unistd_64.h         |   5 +
>  linux-headers/asm-riscv/kvm.h                 |  40 +++++
>  linux-headers/asm-s390/unistd_32.h            |   5 +
>  linux-headers/asm-s390/unistd_64.h            |   5 +
>  linux-headers/asm-x86/kvm.h                   |   3 +
>  linux-headers/asm-x86/unistd_32.h             |   5 +
>  linux-headers/asm-x86/unistd_64.h             |   5 +
>  linux-headers/asm-x86/unistd_x32.h            |   5 +
>  linux-headers/linux/iommufd.h                 |  79 ++++++++++
>  linux-headers/linux/kvm.h                     | 140 +++++++-----------
>  linux-headers/linux/userfaultfd.h             |  29 +++-
>  linux-headers/linux/vfio.h                    |   1 +
>  target/riscv/kvm/kvm-cpu.c                    |  29 ++++
>  24 files changed, 410 insertions(+), 112 deletions(-)
>
> --
> 2.43.2
>
>


      parent reply	other threads:[~2024-03-06  2:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 13:47 [PATCH 0/2] target/riscv/kvm: update KVM exts to Linux 6.8 Daniel Henrique Barboza
2024-03-04 13:47 ` [PATCH 1/2] linux-headers: Update to Linux v6.8-rc6 Daniel Henrique Barboza
2024-03-06  2:09   ` Alistair Francis
2024-03-04 13:47 ` [PATCH 2/2] target/riscv/kvm: update KVM exts to Linux 6.8 Daniel Henrique Barboza
2024-03-06  2:49   ` Alistair Francis
2024-03-06  2:53 ` Alistair Francis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKmqyKMvbLheLiExSgKQEykc7XAgSLw+TZsoKU=etJmi0nkAMw@mail.gmail.com' \
    --to=alistair23@gmail.com \
    --cc=ajones@ventanamicro.com \
    --cc=alistair.francis@wdc.com \
    --cc=bmeng@tinylab.org \
    --cc=dbarboza@ventanamicro.com \
    --cc=liwei1518@gmail.com \
    --cc=palmer@rivosinc.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=zhiwei_liu@linux.alibaba.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).