|
From: | David Hildenbrand |
Subject: | Re: [Qemu-ppc] [Qemu-devel] [PATCH v3 1/3] pc-dimm: factor out MemoryDevice interface |
Date: | Sun, 22 Apr 2018 10:26:44 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
>> +typedef struct MemoryDeviceClass { >> + InterfaceClass parent_class; >> + >> + uint64_t (*get_addr)(MemoryDeviceState *md); >> + uint64_t (*get_plugged_size)(MemoryDeviceState *md, Error **errp); >> + uint64_t (*get_region_size)(MemoryDeviceState *md, Error **errp); > > Just not sure if we need second argument 'Error **errp'? Or all functions > declarations should have this? We need them right now due to the existing implementation of PCDIMM. I don't think we will ever hit such a case (not if anything else is seriously wrong). If nobody has a problem with it, I'll drop these two parameters and directly use &error_abort internally (PCDIMM). Adding Error **errp to functions where we don't expect to be errors doesn't feel right. Thanks for pointing this out! -- Thanks, David / dhildenb
[Prev in Thread] | Current Thread | [Next in Thread] |