On Mon, May 22, 2017 at 01:34:34PM +0200, SF Markus Elfring wrote: > >> Do you find information from a Linux allocation failure report sufficient > >> for any function implementations here? > > > > If kmalloc() and friends guarantee to print a warning and backtrace on > > every allocation failure, then there's no need for error messages in > > callers. > > > > That seems like good justification that can go in the commit > > description, but I'm not sure if kmalloc() and friends guarantee to show > > a message (not just the first time, but for every failed allocation)? > > I am also looking for a more complete and easier accessible documentation > for this aspect of the desired exception handling. > How would we like to resolve any remaining open issues there? No objection from me but please make sure to keep vq_err(). Stefan
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
