<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/arch/arm64/kvm/pvtime.c, branch linux-6.2.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-6.2.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-6.2.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2020-12-03T19:02:18Z</updated>
<entry>
<title>KVM: arm64: Use kvm_write_guest_lock when init stolen time</title>
<updated>2020-12-03T19:02:18Z</updated>
<author>
<name>Keqian Zhu</name>
<email>zhukeqian1@huawei.com</email>
</author>
<published>2020-08-17T11:07:28Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=652d0b701d136ede6bc8a977b3abbe2d420226b9'/>
<id>urn:sha1:652d0b701d136ede6bc8a977b3abbe2d420226b9</id>
<content type='text'>
There is a lock version kvm_write_guest. Use it to simplify code.

Signed-off-by: Keqian Zhu &lt;zhukeqian1@huawei.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Reviewed-by: Andrew Jones &lt;drjones@redhat.com&gt;
Reviewed-by: Steven Price &lt;steven.price@arm.com&gt;
Link: https://lore.kernel.org/r/20200817110728.12196-3-zhukeqian1@huawei.com
</content>
</entry>
<entry>
<title>arm64/x86: KVM: Introduce steal-time cap</title>
<updated>2020-08-21T13:05:19Z</updated>
<author>
<name>Andrew Jones</name>
<email>drjones@redhat.com</email>
</author>
<published>2020-08-04T17:06:04Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=004a01241c5a0d375266ebf1c72f208de99294e9'/>
<id>urn:sha1:004a01241c5a0d375266ebf1c72f208de99294e9</id>
<content type='text'>
arm64 requires a vcpu fd (KVM_HAS_DEVICE_ATTR vcpu ioctl) to probe
support for steal-time. However this is unnecessary, as only a KVM
fd is required, and it complicates userspace (userspace may prefer
delaying vcpu creation until after feature probing). Introduce a cap
that can be checked instead. While x86 can already probe steal-time
support with a kvm fd (KVM_GET_SUPPORTED_CPUID), we add the cap there
too for consistency.

Signed-off-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Reviewed-by: Steven Price &lt;steven.price@arm.com&gt;
Link: https://lore.kernel.org/r/20200804170604.42662-7-drjones@redhat.com
</content>
</entry>
<entry>
<title>KVM: arm64: pvtime: Fix stolen time accounting across migration</title>
<updated>2020-08-21T13:04:14Z</updated>
<author>
<name>Andrew Jones</name>
<email>drjones@redhat.com</email>
</author>
<published>2020-08-04T17:06:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=53f985584e3c2ebe5f2455530fbf87a001528db8'/>
<id>urn:sha1:53f985584e3c2ebe5f2455530fbf87a001528db8</id>
<content type='text'>
When updating the stolen time we should always read the current
stolen time from the user provided memory, not from a kernel
cache. If we use a cache then we'll end up resetting stolen time
to zero on the first update after migration.

Signed-off-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20200804170604.42662-5-drjones@redhat.com
</content>
</entry>
<entry>
<title>KVM: arm64: Drop type input from kvm_put_guest</title>
<updated>2020-08-21T13:04:14Z</updated>
<author>
<name>Andrew Jones</name>
<email>drjones@redhat.com</email>
</author>
<published>2020-08-04T17:06:01Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=4d2d4ce001f283ed8127173543b4cfb65641e357'/>
<id>urn:sha1:4d2d4ce001f283ed8127173543b4cfb65641e357</id>
<content type='text'>
We can use typeof() to avoid the need for the type input.

Suggested-by: Marc Zyngier &lt;maz@kernel.org&gt;
Signed-off-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20200804170604.42662-4-drjones@redhat.com
</content>
</entry>
<entry>
<title>KVM: arm64: pvtime: Fix potential loss of stolen time</title>
<updated>2020-08-21T13:04:14Z</updated>
<author>
<name>Andrew Jones</name>
<email>drjones@redhat.com</email>
</author>
<published>2020-08-04T17:06:00Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=2dbd780e34ac53e79c6c359ce12b89ed665ef562'/>
<id>urn:sha1:2dbd780e34ac53e79c6c359ce12b89ed665ef562</id>
<content type='text'>
We should only check current-&gt;sched_info.run_delay once when
updating stolen time. Otherwise there's a chance there could
be a change between checks that we miss (preemption disabling
comes after vcpu request checks).

Signed-off-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20200804170604.42662-3-drjones@redhat.com
</content>
</entry>
<entry>
<title>KVM: arm64: pvtime: steal-time is only supported when configured</title>
<updated>2020-08-21T13:04:14Z</updated>
<author>
<name>Andrew Jones</name>
<email>drjones@redhat.com</email>
</author>
<published>2020-08-04T17:05:59Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=38480df564cc68f081bb38998927d164b9010995'/>
<id>urn:sha1:38480df564cc68f081bb38998927d164b9010995</id>
<content type='text'>
Don't confuse the guest by saying steal-time is supported when
it hasn't been configured by userspace and won't work.

Signed-off-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20200804170604.42662-2-drjones@redhat.com
</content>
</entry>
<entry>
<title>KVM: arm64: pvtime: Ensure task delay accounting is enabled</title>
<updated>2020-06-22T14:35:57Z</updated>
<author>
<name>Andrew Jones</name>
<email>drjones@redhat.com</email>
</author>
<published>2020-06-22T14:27:10Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a25e91028ac2f544e0140aff2c9360a0e995dd86'/>
<id>urn:sha1:a25e91028ac2f544e0140aff2c9360a0e995dd86</id>
<content type='text'>
Ensure we're actually accounting run_delay before we claim that we'll
expose it to the guest. If we're not, then we just pretend like steal
time isn't supported in order to avoid any confusion.

Signed-off-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20200622142710.18677-1-drjones@redhat.com
</content>
</entry>
<entry>
<title>KVM: arm64: Move virt/kvm/arm to arch/arm64</title>
<updated>2020-05-16T14:03:59Z</updated>
<author>
<name>Marc Zyngier</name>
<email>maz@kernel.org</email>
</author>
<published>2020-05-13T10:40:34Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=9ed24f4b712b855dcf7be3025b75b051cb73a2b7'/>
<id>urn:sha1:9ed24f4b712b855dcf7be3025b75b051cb73a2b7</id>
<content type='text'>
Now that the 32bit KVM/arm host is a distant memory, let's move the
whole of the KVM/arm64 code into the arm64 tree.

As they said in the song: Welcome Home (Sanitarium).

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Acked-by: Will Deacon &lt;will@kernel.org&gt;
Link: https://lore.kernel.org/r/20200513104034.74741-1-maz@kernel.org
</content>
</entry>
</feed>
