From: Nadav Amit <nadav.amit@gmail.com>
To: Javier Romero <xavinux@gmail.com>
Cc: like.xu@intel.com, Liran Alon <liran.alon@oracle.com>,
kvmarm@lists.cs.columbia.edu, kvm <kvm@vger.kernel.org>
Subject: Re: Contribution to KVM.
Date: Thu, 9 Apr 2020 20:52:57 -0700 [thread overview]
Message-ID: <2E118FCA-7AB1-480F-8F49-3EFD77CC2992@gmail.com> (raw)
In-Reply-To: <c86002a6-d613-c0be-a672-cca8e9c83e1c@intel.com>
> On Apr 9, 2020, at 8:34 PM, Xu, Like <like.xu@intel.com> wrote:
>
> On 2020/4/10 5:29, Javier Romero wrote:
>> Hello,
>>
>> My name is Javier, live in Argentina and work as a cloud engineer.
>>
>> Have been working with Linux servers for the last 10 years in an
>> Internet Service Provider and I'm interested in contributing to KVM
> Welcome, I'm a newbie as well.
>> maybe with testing as a start point.
> You may try the http://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
> and tools/testing/selftests/kvm in the kernel tree.
>> If it can be useful to test KVM on ARM, I have a Raspberry PI 3 at disposal.
> If you test KVM on Intel platforms, you will definitely get support from me :D.
If you are looking for something specific, here are two issues with
relatively limited scope, which AFAIK were not resolved:
1. Shadow VMCS bug, which is also a test bug [1]. You can start by fixing
the test and then fix KVM.
2. Try to run the tests with more than 4GB of memory. The last time I tried
(actually by running the test on bare metal), the INIT test that Liran
wrote failed.
Regards,
Nadav
[1] https://lore.kernel.org/kvm/3235DBB0-0DC0-418C-BC45-A4B78612E273@gmail.com/T/#u
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2020-04-10 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 21:29 Contribution to KVM Javier Romero
2020-04-10 3:34 ` Xu, Like
2020-04-10 3:52 ` Nadav Amit [this message]
2020-04-10 4:49 ` Javier Romero
2020-04-10 10:20 ` Liran Alon
2020-04-10 19:41 ` Nadav Amit
2020-04-10 3:54 ` Javier Romero
2020-04-10 3:56 ` Javier Romero
2020-04-10 4:43 ` Javier Romero
2020-04-10 7:49 ` Marc Zyngier
2020-04-10 20:15 ` Javier Romero
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=2E118FCA-7AB1-480F-8F49-3EFD77CC2992@gmail.com \
--to=nadav.amit@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=like.xu@intel.com \
--cc=liran.alon@oracle.com \
--cc=xavinux@gmail.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