1. 04 7月, 2018 1 次提交
  2. 22 6月, 2018 2 次提交
  3. 21 6月, 2018 3 次提交
  4. 15 6月, 2018 1 次提交
  5. 11 6月, 2018 1 次提交
  6. 09 6月, 2018 2 次提交
  7. 08 6月, 2018 1 次提交
  8. 07 6月, 2018 2 次提交
  9. 05 6月, 2018 1 次提交
  10. 31 5月, 2018 1 次提交
  11. 26 5月, 2018 1 次提交
  12. 27 3月, 2018 1 次提交
  13. 24 3月, 2018 1 次提交
    • E
      qapi: Force UTF8 encoding when parsing qapi files · 39615354
      Eric Blake 提交于
      Commit d4e5ec87 already fixed things to work around Python 3's
      lame bug of having LC_ALL=C not be 8-bit clean, when parsing the
      main QMP qapi files; but failed to do likewise in the tests
      directory.  As a result, running 'LC_ALL=C make check' fails on
      escape-too-big and unicode-str when using python 3 with a nasty
      stack trace instead of the intended graceful error message that
      QAPI doesn't yet support 8-bit data (the two tests contain
      Unicode é, when parsed in UTF-8; they represent something
      different when parsed in a proper single-byte C locale, but that
      doesn't matter to the error message printed out, provided that
      brain-dead Python hasn't first choked on the input instead of
      being 8-bit clean).
      
      Ideally, we'd teach the qapi generator scripts to automatically
      slurp things in using UTF-8 regardless of locale, and to honor
      content that is not limited to 7 bit data rather than gracefully
      erroring out; but until then, since our graceful error depends
      on python parsing 8-bit data (even if nothing we generate uses
      8-bit data), our quick fix is to use the right locale when
      running these tests.
      Reported-by: NPeter Maydell <peter.maydell@linaro.org>
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Message-Id: <20180319205040.1113423-1-eblake@redhat.com>
      Reviewed-by: NDaniel P. Berrangé <berrange@redhat.com>
      39615354
  14. 20 3月, 2018 2 次提交
  15. 14 3月, 2018 2 次提交
  16. 03 3月, 2018 4 次提交
  17. 23 2月, 2018 1 次提交
  18. 21 2月, 2018 2 次提交
  19. 14 2月, 2018 5 次提交
  20. 13 2月, 2018 2 次提交
  21. 06 2月, 2018 1 次提交
  22. 05 2月, 2018 1 次提交
  23. 30 1月, 2018 1 次提交
    • M
      tpm: add CRB device · 4ab6cb4c
      Marc-André Lureau 提交于
      tpm_crb is a device for TPM 2.0 Command Response Buffer (CRB)
      Interface as defined in TCG PC Client Platform TPM Profile (PTP)
      Specification Family “2.0” Level 00 Revision 01.03 v22.
      
      The PTP allows device implementation to switch between TIS and CRB
      model at run time, but given that CRB is a simpler device to
      implement, I chose to implement it as a different device.
      
      The device doesn't implement other locality than 0 for now (my laptop
      TPM doesn't either, so I assume this isn't so bad)
      
      Tested with some success with Linux upstream and Windows 10, seabios &
      modified ovmf. The device is recognized and correctly transmit
      command/response with passthrough & emu. However, we are missing PPI
      ACPI part atm.
      Signed-off-by: NMarc-André Lureau <marcandre.lureau@redhat.com>
      Reviewed-by: NStefan Berger <stefanb@linux.vnet.ibm.com>
      Signed-off-by: NStefan Berger <stefanb@linux.vnet.ibm.com>
      4ab6cb4c
  24. 22 1月, 2018 1 次提交