From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Maydell Subject: Re: [Android-virt] [PATCH v9 16/16] ARM: KVM: Guest wait-for-interrupts (WFI) support Date: Tue, 3 Jul 2012 14:14:55 +0100 Message-ID: References: <20120703085841.27746.82730.stgit@ubuntu> <20120703090212.27746.39517.stgit@ubuntu> <4FF2EF5F.8070207@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Christoffer Dall , tech@virtualopensystems.com, kvm@vger.kernel.org, android-virt@lists.cs.columbia.edu To: Avi Kivity Return-path: Received: from mail-bk0-f46.google.com ([209.85.214.46]:54776 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756358Ab2GCNO5 (ORCPT ); Tue, 3 Jul 2012 09:14:57 -0400 Received: by bkwj10 with SMTP id j10so1597868bkw.19 for ; Tue, 03 Jul 2012 06:14:55 -0700 (PDT) In-Reply-To: <4FF2EF5F.8070207@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 3 July 2012 14:10, Avi Kivity wrote: > Or you could just call kvm_vcpu_block() here without having the > variable. But eventually you'll need it since you want to expose wfi > state to userspace for live migration. You could just always wake the cpu when migrating: the architecture allows WFI to return early for any reason it likes including implementation convenience. -- PMM