This will be useful when the functions are called, early in the configure
process, to filter out targets that do not support hardware acceleration.
Reviewed-by: Richard Henderson
Reviewed-by: Daniel P. Berrange
Signed-off-by: Paolo Bonzini
On Tue, Jul 04, 2017 at 11:44:41AM +0200, Paolo Bonzini wrote:
>
>
> On 04/07/2017 10:28, Daniel P. Berrange wrote:
> >> +supported_kvm_target() {
> >> +test "$kvm" = "yes" || return 1
> >> +glob "$1" "*-softmmu" || return 1
> >> +case "${1%-softmmu}:$cpu" in
> >> +arm:arm |
On 04/07/2017 10:28, Daniel P. Berrange wrote:
>> +supported_kvm_target() {
>> +test "$kvm" = "yes" || return 1
>> +glob "$1" "*-softmmu" || return 1
>> +case "${1%-softmmu}:$cpu" in
>> +arm:arm | aarch64:aarch64 | \
>> +i386:i386 | i386:x86_64 | i386:x32 | \
>> +
On Mon, Jul 03, 2017 at 06:34:32PM +0200, Paolo Bonzini wrote:
> This will be useful when the functions are called, early in the configure
> process, to filter out targets that do not support hardware acceleration.
>
> Signed-off-by: Paolo Bonzini
> ---
> configure | 90
>
On 07/03/2017 09:34 AM, Paolo Bonzini wrote:
This will be useful when the functions are called, early in the configure
process, to filter out targets that do not support hardware acceleration.
Signed-off-by: Paolo Bonzini
---
configure | 90
This will be useful when the functions are called, early in the configure
process, to filter out targets that do not support hardware acceleration.
Signed-off-by: Paolo Bonzini
---
configure | 90 ++-
1 file