<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/arm64/kvm/arch_timer.c, branch linux-5.13.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.13.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.13.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2020-12-23T16:43:12Z</updated>
<entry>
<title>KVM: arm64: arch_timer: Remove VGIC initialization check</title>
<updated>2020-12-23T16:43:12Z</updated>
<author>
<name>Alexandru Elisei</name>
</author>
<published>2020-12-01T15:01:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f16570ba47ff2b3766ebeaba6f4b80ad48cfd6a1'/>
<id>urn:sha1:f16570ba47ff2b3766ebeaba6f4b80ad48cfd6a1</id>
<content type='text'>
kvm_timer_enable() is called in kvm_vcpu_first_run_init() after
kvm_vgic_map_resources() if the VGIC wasn't ready. kvm_vgic_map_resources()
is the only place where kvm-&gt;arch.vgic.ready is set to true.

For a v2 VGIC, kvm_vgic_map_resources() will attempt to initialize the VGIC
and set the initialized flag.

For a v3 VGIC, kvm_vgic_map_resources() will return an error code if the
VGIC isn't already initialized.

The end result is that if we've reached kvm_timer_enable(), the VGIC is
initialzed and ready and vgic_initialized() will always be true, so remove
this check.

Signed-off-by: Alexandru Elisei &lt;alexandru.elisei@arm.com&gt;
Reviewed-by: Eric Auger &lt;eric.auger@redhat.com&gt;
[maz: added comment about vgic initialisation, as suggested by Eric]
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20201201150157.223625-3-alexandru.elisei@arm.com
</content>
</entry>
<entry>
<title>KVM: arm64: timers: Move timer registers to the sys_regs file</title>
<updated>2020-07-07T08:28:38Z</updated>
<author>
<name>Marc Zyngier</name>
</author>
<published>2019-06-28T14:23:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=41ce82f63c0624556b94b90551e4f70a0c913879'/>
<id>urn:sha1:41ce82f63c0624556b94b90551e4f70a0c913879</id>
<content type='text'>
Move the timer gsisters to the sysreg file. This will further help when
they are directly changed by a nesting hypervisor in the VNCR page.

This requires moving the initialisation of the timer struct so that some
of the helpers (such as arch_timer_ctx_index) can work correctly at an
early stage.

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</content>
</entry>
<entry>
<title>KVM: arm64: timers: Rename kvm_timer_sync_hwstate to kvm_timer_sync_user</title>
<updated>2020-07-07T08:28:38Z</updated>
<author>
<name>Marc Zyngier</name>
</author>
<published>2020-04-22T07:58:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3c5ff0c60f2febb170bc4096d4b8a8390ebb0bad'/>
<id>urn:sha1:3c5ff0c60f2febb170bc4096d4b8a8390ebb0bad</id>
<content type='text'>
kvm_timer_sync_hwstate() has nothing to do with the timer HW state,
but more to do with the state of a userspace interrupt controller.
Change the suffix from _hwstate to_user, in keeping with the rest
of the code.

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'kvmarm-5.8' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD</title>
<updated>2020-06-01T08:26:27Z</updated>
<author>
<name>Paolo Bonzini</name>
</author>
<published>2020-06-01T08:26:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=380609445cff6ee7b6c7e43bbdc953985b45a6ed'/>
<id>urn:sha1:380609445cff6ee7b6c7e43bbdc953985b45a6ed</id>
<content type='text'>
KVM/arm64 updates for Linux 5.8:

- Move the arch-specific code into arch/arm64/kvm
- Start the post-32bit cleanup
- Cherry-pick a few non-invasive pre-NV patches
</content>
</entry>
<entry>
<title>KVM: arm64: Simplify __kvm_timer_set_cntvoff implementation</title>
<updated>2020-05-16T14:04:18Z</updated>
<author>
<name>Marc Zyngier</name>
</author>
<published>2020-05-13T10:58:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c6fe89ff8b250ad4dc4bed7bd5877bfbc35f4aba'/>
<id>urn:sha1:c6fe89ff8b250ad4dc4bed7bd5877bfbc35f4aba</id>
<content type='text'>
Now that this function isn't constrained by the 32bit PCS,
let's simplify it by taking a single 64bit offset instead
of two 32bit parameters.

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</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>
</author>
<published>2020-05-13T10:40:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/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>
