[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64
|
From: |
Peter Xu |
|
Subject: |
Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64 |
|
Date: |
Tue, 30 Jan 2024 18:48:04 +0800 |
On Tue, Jan 30, 2024 at 10:18:07AM +0000, Peter Maydell wrote:
> On Mon, 29 Jan 2024 at 23:31, Fabiano Rosas <farosas@suse.de> wrote:
> >
> > Fabiano Rosas <farosas@suse.de> writes:
> >
> > > Peter Xu <peterx@redhat.com> writes:
> > >
> > >> On Fri, Jan 26, 2024 at 11:54:32AM -0300, Fabiano Rosas wrote:
> > > The issue that occurs to me now is that 'cpu host' will not work with
> > > TCG. We might actually need to go poking /dev/kvm for this to work.
> >
> > Nevermind this last part. There's not going to be a scenario where we
> > build with CONFIG_KVM, but run in an environment that does not support
> > KVM.
>
> Yes, there is. We'll build with CONFIG_KVM on any aarch64 host,
> but that doesn't imply that the user running the build and
> test has permissions for /dev/kvm.
I'm actually pretty confused on why this would be a problem even for
neoverse-n1: can we just try to use KVM, if it fails then use TCG?
Something like:
(construct qemu cmdline)
..
#ifdef CONFIG_KVM
"-accel kvm "
#endif
"-accel tcg "
..
?
IIUC if we specify two "-accel", we'll try the first, then if failed then
the 2nd?
--
Peter Xu
- [PULL 04/15] migration: Drop unnecessary check in ram's pending_exact(), (continued)
- [PULL 04/15] migration: Drop unnecessary check in ram's pending_exact(), peterx, 2024/01/25
- [PULL 05/15] analyze-migration.py: Remove trick on parsing ramblocks, peterx, 2024/01/25
- [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, peterx, 2024/01/25
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Fabiano Rosas, 2024/01/26
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Peter Maydell, 2024/01/26
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Fabiano Rosas, 2024/01/26
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Peter Xu, 2024/01/28
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Fabiano Rosas, 2024/01/29
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Fabiano Rosas, 2024/01/29
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Peter Maydell, 2024/01/30
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64,
Peter Xu <=
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Fabiano Rosas, 2024/01/30
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Peter Xu, 2024/01/30
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Fabiano Rosas, 2024/01/31
- Re: [PULL 06/15] tests/qtest/migration: Don't use -cpu max for aarch64, Peter Xu, 2024/01/31
[PULL 07/15] ci: Add a migration compatibility test job, peterx, 2024/01/25
[PULL 08/15] ci: Disable migration compatibility tests for aarch64, peterx, 2024/01/25
[PULL 09/15] migration/yank: Use channel features, peterx, 2024/01/25
[PULL 10/15] migration: Fix use-after-free of migration state object, peterx, 2024/01/25
[PULL 11/15] migration: Take reference to migration state around bg_migration_vm_start_bh, peterx, 2024/01/25
[PULL 12/15] migration: Reference migration state around loadvm_postcopy_handle_run_bh, peterx, 2024/01/25