[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH RFC V2 1/6] xen: Emulate with no writes


  • To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxx
  • From: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
  • Date: Mon, 14 Jul 2014 11:37:29 +0300
  • Cc: mdontu@xxxxxxxxxxxxxxx, tim@xxxxxxx, JBeulich@xxxxxxxx
  • Comment: DomainKeys? See http://domainkeys.sourceforge.net/
  • Delivery-date: Mon, 14 Jul 2014 08:36:55 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bitdefender.com; b=QkyqVqSAMM/G/JQM20/lcei4HpjG8Zf9aLf+XlyeuFQYH6FKKayAnWES0zUWK12Q4n5Ii9I9tTYWML8uvkRTFJlARUYVozpti8+6Iyr4pKo+CLN0OG7iLaFKkm9KCnFopye0JPfp5ZEWXkazbbkX0IWx+E59ZmPpxMu/7mBr3VgM8gPCsOGnXVFm4Lwfwvn6XPqYsZy/rOUSgU78OwzotV5y6DdINdZgkeJzq3wxnoxYpHIriF1w99s/0s/k8Jiyzikf0rKSDZUlNbqaaOOiHuFsKB0RenK9zD+VPE3+skDYQgvPEFiLohHZj2D3UZqVIxbWDQt9yYy2RVkhcA8x3g==; h=Received:Received:Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-BitDefender-Scanner:X-BitDefender-Spam:X-BitDefender-SpamStamp:X-BitDefender-CF-Stamp;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 07/11/2014 07:23 PM, Andrew Cooper wrote:
> On 11/07/14 16:43, Razvan Cojocaru wrote:
>> +void hvm_emulate_one_full(bool_t nowrite,
>> +    unsigned int unhandleable_trapnr,
>> +    int unhandleable_errcode)
>> +{
>> +    struct hvm_emulate_ctxt ctx[1] = {};
> 
> This construct looks suspect.  What is wrong with
> 
> struct hvm_emulate_ctxt ctx = { 0 }; and using &ctx below ?

Modifying the code to address your comments, that code was written to
get around a GCC issue:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119

It's either that or writing

struct hvm_emulate_ctxt ctx = {{ 0 }};

I've changed it to the latter.


Thanks,
Razvan Cojocaru

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.