GitHub PushEvent at 2014-10-29 16:00:44
Repository: xen
Actor: olafhering
Payload: {"shas":[["607e8494c42397fb249191904066cace6ac9a880","e941dd2dd940d198dc2651f51bd002f65d602f78@Intel.com","vmx: fix save/restore issue with apicv\n\nThis patch fixes two issues:\n\n1. Interrupts on PIR are lost during save/restore. Syncing the PIR\ninto IRR during save will fix it.\n\n2. EOI exit bitmap doesn't set up correctly after restore. Here we\nwill construct the eoi exit bitmap via (IRR | ISR). Though it may cause\nunnecessary eoi exit of the interrupts that pending in IRR or ISR during\nsave/restore, each pending interrupt only causes one vmexit. The\nsubsequent interrupts will adjust the eoi exit bitmap correctly. So\nthe performance hurt can be ignored.\n\nSigned-off-by: Yang Zhang <yang.z.zhang@Intel.com>\nSigned-off-by: Olaf Hering <olaf@aepfle.de>\nReviewed-by: Jan Beulich <jbeulich@suse.com>\nReviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>","Yang Zhang",true],["66d0c0aa1f3e57e873fd64d1d370e11758d25442","cb880bd9232cc23a76ddb35f95d96ed0ad981f23@citrix.com","hvm/load: correct length checks for zeroextended records\n\nIn the case that Xen is attempting to load a zeroextended HVM record where the\ndifference needing extending would overflow the data blob, _hvm_check_entry()\nwill incorrectly fail before working out that it would have been safe.\n\nThe \"len + sizeof(*d)\" check is wrong.  Consider zeroextending a 16 byte\nrecord into a 32 byte structure.  \"32 + hdr\" will fail the overall context\nlength check even though the pre-extended record in the stream is 16 bytes.\n\nThe first condition is reduced to just a length check for hvm save header,\nwhile the second condition is extended to include a check that the record in\nthe stream not exceeding the stream length.\n\nThe error messages are extended to include further useful information.\n\nSigned-off-by: Andrew Cooper <andrew.cooper3@citrix.com>\nReviewed-by: Paul Durrant <Paul.Durrant@citrix.com>\nReviewed-by: Jan Beulich <jbeulich@suse.com>","Andrew Cooper",true],["e65436ba36be8f1b735573d8fc9af7d8a053ba5f","01de09643e0ae62e116f8bd77de435799874b456@suse.com","x86: tolerate running on EFI runtime services page tables in map_domain_page()\n\nIn the event of a #PF while in an EFI runtime service function we\notherwise can't dump the page tables, making the analysis of the\nproblem more cumbersome.\n\nSigned-off-by: Jan Beulich <jbeulich@suse.com>\nReviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>","Jan Beulich",true],["5680244040d26234a43c7f884ecf98fa4928d0da","01de09643e0ae62e116f8bd77de435799874b456@suse.com","EFI: allow to suppress the use of runtime services\n\nOn certain systems some of the memory map entries designated for use by\nruntime services cannot be mapped (frequently due to firmware bugs). On\nothers, some of the memory map entries aren't even marked for runtime\nservices use, yet are being used by them. For both cases give people a\nway to suppress use of runtime services altogether.\n\nSigned-off-by: Jan Beulich <jbeulich@suse.com>\nReviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>","Jan Beulich",true],["4ed4dc689761a5597a492aeef89aff50cd9b39ef","01de09643e0ae62e116f8bd77de435799874b456@suse.com","EFI: constify a few table pointers\n\nWe shouldn't (and don't) modify any of these tables.\n\nSigned-off-by: Jan Beulich <jbeulich@suse.com>\nReviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>","Jan Beulich",true],["d7bb8e88a087690feba63ef83c13ba067f041da0","ecf39397e8766c0b6096951cf917fd38dd62a890@verizon.com","x86/HVM: sanity check xsave area when migrating or restoring from older Xen versions\n\nXen 4.3.0, 4.2.3 and older transferred a maximum sized xsave area (as\nif all the available XCR0 bits were set); the new version only\ntransfers based on the actual XCR0 bits. This may result in a smaller\narea if the last sections were missing (e.g., the LWP area from an AMD\nmachine). If the size doesn't match the XCR0 derived size, the size is\nchecked against the maximum size and the part of the xsave area\nbetween the actual and maximum used size is checked for zero data. If\neither the max size check or any part of the overflow area is\nnon-zero, we return with an error.\n\nSigned-off-by: Don Koch <dkoch@verizon.com>\nReviewed-by: Jan Beulich <jbeulich@suse.com>\nReviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>","Don Koch",true],["0f2bde078ace619fe8e26730495b6ef2c3a2e9bf","86aa98d1ce79e67acc7976f5603381a6ff7f6a6e@intel.com","vtd: correct some comments\n\nIn some cases Dom0 and hardware domain are not one same domain.\n\nSigned-off-by: Tiejun Chen <tiejun.chen@intel.com>","Tiejun Chen",true]],"size":7,"ref":"refs/heads/staging","head":"0f2bde078ace619fe8e26730495b6ef2c3a2e9bf"}