Skip to content
Permalink
Branch: block-next
Commits on Sep 12, 2019
  1. util/ioc.c: try to reassure Coverity about qemu_iovec_init_extended

    Vladimir Sementsov-Ogievskiy Stefan Hajnoczi
    Vladimir Sementsov-Ogievskiy authored and Stefan Hajnoczi committed Sep 10, 2019
    Make it more obvious, that filling qiov corresponds to qiov allocation,
    which in turn corresponds to total_niov calculation, based on mid_niov
    (not mid_len). Still add an assertion to show that there should be no
    difference.
    
    Reported-by: Coverity (CID 1405302)
    Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
    Message-id: 20190910090310.14032-1-vsementsov@virtuozzo.com
    Suggested-by: Peter Maydell <peter.maydell@linaro.org>
    Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
    Message-Id: <20190910090310.14032-1-vsementsov@virtuozzo.com>
    Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
  2. docs/nvdimm: add example on persistent backend setup

    Wei Yang Stefan Hajnoczi
    Wei Yang authored and Stefan Hajnoczi committed Aug 1, 2019
    Persistent backend setup requires some knowledge about nvdimm and ndctl
    tool. Some users report they may struggle to gather these knowledge and
    have difficulty to setup it properly.
    
    Here we provide two examples for persistent backend and gives the link
    to ndctl. By doing so, user could try it directly and do more
    investigation on persistent backend setup with ndctl.
    
    Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
    Reviewed-by: Pankaj Gupta <pagupta@redhat.com>
    Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
    Message-id: 20190801004053.7021-1-richardw.yang@linux.intel.com
    
    Message-Id: <20190801004053.7021-1-richardw.yang@linux.intel.com>
    Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Commits on Sep 9, 2019
  1. Merge remote-tracking branch 'remotes/huth-gitlab/tags/m68k-pull-2019…

    pm215 committed Sep 9, 2019
    …-09-07' into staging
    
    Add the m68k next-cube machine
    
    # gpg: Signature made Sat 07 Sep 2019 16:32:53 BST
    # gpg:                using RSA key 27B88847EEE0250118F3EAB92ED9D774FE702DB5
    # gpg:                issuer "huth@tuxfamily.org"
    # gpg: Good signature from "Thomas Huth <th.huth@gmx.de>" [full]
    # gpg:                 aka "Thomas Huth <thuth@redhat.com>" [full]
    # gpg:                 aka "Thomas Huth <huth@tuxfamily.org>" [full]
    # gpg:                 aka "Thomas Huth <th.huth@posteo.de>" [unknown]
    # Primary key fingerprint: 27B8 8847 EEE0 2501 18F3  EAB9 2ED9 D774 FE70 2DB5
    
    * remotes/huth-gitlab/tags/m68k-pull-2019-09-07:
      .travis.yml: Let the avocado job run the NeXTcube tests
      tests/acceptance: Add test of NeXTcube framebuffer using OCR
      m68k: Add an entry for the NeXTcube machine to the MAINTAINERS file
      m68k: Add serial controller to the NeXTcube machine
      escc: introduce a selector for the register bit
      m68k: Add NeXTcube machine
      m68k: Add NeXTcube keyboard device
      m68k: Add NeXTcube framebuffer device emulation
    
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Commits on Sep 7, 2019
  1. .travis.yml: Let the avocado job run the NeXTcube tests

    philmd authored and huth committed Aug 13, 2019
    Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
    Message-Id: <20190813134921.30602-3-philmd@redhat.com>
    [huth: Rebased patch to master branch]
    Signed-off-by: Thomas Huth <huth@tuxfamily.org>
  2. tests/acceptance: Add test of NeXTcube framebuffer using OCR

    philmd authored and huth committed Aug 13, 2019
    Add a test of the NeXTcube framebuffer using the Tesseract OCR
    engine on a screenshot of the framebuffer device.
    
    The test is very quick:
    
      $ avocado --show=app,console run tests/acceptance/machine_m68k_nextcube.py
      JOB ID     : 78844a92424cc495bd068c3874d542d1e20f24bc
      JOB LOG    : /home/phil/avocado/job-results/job-2019-08-13T13.16-78844a9/job.log
       (1/3) tests/acceptance/machine_m68k_nextcube.py:NextCubeMachine.test_bootrom_framebuffer_size: PASS (2.16 s)
       (2/3) tests/acceptance/machine_m68k_nextcube.py:NextCubeMachine.test_bootrom_framebuffer_ocr_with_tesseract_v3: -
      ue r pun Honl'flx ; 5‘ 55‘
      avg ncaaaaa 25 MHZ, memary jag m
      Backplane slat «a
      Ethernet address a a r a r3 2
      Memgry sackets aea canflqured far 16MB Darlly page made stMs but have 16MB page made stMs )nstalled
      Memgry sackets a and 1 canflqured far 16MB Darlly page made stMs but have 16MB page made stMs )nstalled
      [...]
      Yestlnq the rpu, 5::
      system test raneg Errar egge 51
      Egg: cammand
      Default pggc devlce nut fauna
      NEXY>I
      PASS (2.64 s)
       (3/3) tests/acceptance/machine_m68k_nextcube.py:NextCubeMachine.test_bootrom_framebuffer_ocr_with_tesseract_v4: SKIP: tesseract v4 OCR tool not available
      RESULTS    : PASS 2 | ERROR 0 | FAIL 0 | SKIP 1 | WARN 0 | INTERRUPT 0 | CANCEL 0
      JOB TIME   : 5.35 s
    
    Documentation on how to install tesseract:
      https://github.com/tesseract-ocr/tesseract/wiki#installation
    
    Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
    Message-Id: <20190813134921.30602-2-philmd@redhat.com>
    Signed-off-by: Thomas Huth <huth@tuxfamily.org>
  3. m68k: Add an entry for the NeXTcube machine to the MAINTAINERS file

    huth committed Jun 30, 2018
    I don't have much clue about the NeXT hardware, but at least I know now
    the source files a little bit, so I volunteer to pick up patches and send
    PULL requests for them until someone else with more knowledge steps up
    to do this job instead.
    
    Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Message-Id: <20190831074519.32613-7-huth@tuxfamily.org>
    Signed-off-by: Thomas Huth <huth@tuxfamily.org>
  4. m68k: Add serial controller to the NeXTcube machine

    huth committed Jun 30, 2018
    The NeXTcube uses a normal 8530 serial controller, so we can simply use
    our normal "escc" device here.
    While we're at it, also add a boot-serial-test for the next-cube machine,
    now that the serial output works.
    
    Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Message-Id: <20190831074519.32613-6-huth@tuxfamily.org>
    Signed-off-by: Thomas Huth <huth@tuxfamily.org>
  5. escc: introduce a selector for the register bit

    vivier authored and huth committed May 25, 2019
    On Sparc and PowerMac, the bit 0 of the address selects the register
    type (control or data) and bit 1 selects the channel (B or A).
    
    On m68k Macintosh and NeXTcube, the bit 0 selects the channel and
    bit 1 the register type.
    
    This patch introduces a new parameter (bit_swap) to the device interface
    to indicate bits usage must be swapped between registers and channels.
    
    For the moment all the machines use the bit 0, but this change will be
    needed to emulate the Quadra 800 or NeXTcube machine.
    
    Signed-off-by: Laurent Vivier <laurent@vivier.eu>
    Reviewed-by: Hervé Poussineau <hpoussin@reactos.org>
    [thh: added NeXTcube to the patch description]
    Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Message-Id: <20190831074519.32613-5-huth@tuxfamily.org>
    Signed-off-by: Thomas Huth <huth@tuxfamily.org>
  6. m68k: Add NeXTcube machine

    huth committed Jun 30, 2018
    It is still quite incomplete (no SCSI, no floppy emulation, no network,
    etc.), but the firmware already shows up the debug monitor prompt in the
    framebuffer display, so at least the very basics are already working.
    
    This code has been taken from Bryce Lanham's GSoC 2011 NeXT branch at
    
     https://github.com/blanham/qemu-NeXT/blob/next-cube/hw/next-cube.c
    
    and altered quite a bit to fit the latest interface and coding conventions
    of the current QEMU.
    
    Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Message-Id: <20190831074519.32613-4-huth@tuxfamily.org>
    Signed-off-by: Thomas Huth <huth@tuxfamily.org>
  7. m68k: Add NeXTcube keyboard device

    huth committed Jun 30, 2018
    It is likely still quite incomplete (e.g. mouse and interrupts are not
    implemented yet), but it is good enough for keyboard input at the firmware
    monitor.
    This code has been taken from Bryce Lanham's GSoC 2011 NeXT branch at
    
     https://github.com/blanham/qemu-NeXT/blob/next-cube/hw/next-kbd.c
    
    and altered to fit the latest interface of the current QEMU (e.g. to use
    memory_region_init_io() instead of cpu_register_physical_memory()).
    
    Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Message-Id: <20190831074519.32613-3-huth@tuxfamily.org>
    Signed-off-by: Thomas Huth <huth@tuxfamily.org>
  8. m68k: Add NeXTcube framebuffer device emulation

    huth committed Jun 30, 2018
    The NeXTcube uses a linear framebuffer with 4 greyscale colors and
    a fixed resolution of 1120 * 832.
    This code has been taken from Bryce Lanham's GSoC 2011 NeXT branch at
    
     https://github.com/blanham/qemu-NeXT/blob/next-cube/hw/next-fb.c
    
    and altered to fit the latest interface of the current QEMU (e.g.
    the device has been "qdev"-ified etc.).
    
    Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Message-Id: <20190831074519.32613-2-huth@tuxfamily.org>
    Signed-off-by: Thomas Huth <huth@tuxfamily.org>
Commits on Sep 6, 2019
  1. Merge remote-tracking branch 'remotes/ericb/tags/pull-nbd-2019-09-05-…

    pm215 committed Sep 6, 2019
    …v2' into staging
    
    nbd patches for 2019-09-05
    
    - Advertise NBD_FLAG_CAN_MULTI_CONN on readonly images
    - Tolerate larger set of server error responses during handshake
    - More precision on handling fallocate() failures due to alignment
    - Better documentation of NBD connection URIs
    - Implement new extension NBD_CMD_FLAG_FAST_ZERO to benefit qemu-img convert
    
    # gpg: Signature made Thu 05 Sep 2019 22:08:17 BST
    # gpg:                using RSA key 71C2CC22B1C4602927D2F3AAA7A16B4A2527436A
    # gpg: Good signature from "Eric Blake <eblake@redhat.com>" [full]
    # gpg:                 aka "Eric Blake (Free Software Programmer) <ebb9@byu.net>" [full]
    # gpg:                 aka "[jpeg image of size 6874]" [full]
    # Primary key fingerprint: 71C2 CC22 B1C4 6029 27D2  F3AA A7A1 6B4A 2527 436A
    
    * remotes/ericb/tags/pull-nbd-2019-09-05-v2:
      nbd: Implement server use of NBD FAST_ZERO
      nbd: Implement client use of NBD FAST_ZERO
      nbd: Prepare for NBD_CMD_FLAG_FAST_ZERO
      nbd: Improve per-export flag handling in server
      docs: Update preferred NBD device syntax
      block: workaround for unaligned byte range in fallocate()
      nbd: Tolerate more errors to structured reply request
      nbd: Use g_autofree in a few places
      nbd: Advertise multi-conn for shared read-only connections
    
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Commits on Sep 5, 2019
  1. nbd: Implement server use of NBD FAST_ZERO

    ebblake committed Aug 23, 2019
    The server side is fairly straightforward: we can always advertise
    support for detection of fast zero, and implement it by mapping the
    request to the block layer BDRV_REQ_NO_FALLBACK.
    
    Signed-off-by: Eric Blake <eblake@redhat.com>
    Message-Id: <20190823143726.27062-5-eblake@redhat.com>
    Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
    [eblake: update iotests 223, 233]
  2. nbd: Implement client use of NBD FAST_ZERO

    ebblake committed Aug 23, 2019
    The client side is fairly straightforward: if the server advertised
    fast zero support, then we can map that to BDRV_REQ_NO_FALLBACK
    support.  A server that advertises FAST_ZERO but not WRITE_ZEROES
    is technically broken, but we can ignore that situation as it does
    not change our behavior.
    
    Signed-off-by: Eric Blake <eblake@redhat.com>
    Message-Id: <20190823143726.27062-4-eblake@redhat.com>
    Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
  3. nbd: Prepare for NBD_CMD_FLAG_FAST_ZERO

    ebblake committed Aug 23, 2019
    Commit fe0480d and friends added BDRV_REQ_NO_FALLBACK as a way to
    avoid wasting time on a preliminary write-zero request that will later
    be rewritten by actual data, if it is known that the write-zero
    request will use a slow fallback; but in doing so, could not optimize
    for NBD.  The NBD specification is now considering an extension that
    will allow passing on those semantics; this patch updates the new
    protocol bits and 'qemu-nbd --list' output to recognize the bit, as
    well as the new errno value possible when using the new flag; while
    upcoming patches will improve the client to use the feature when
    present, and the server to advertise support for it.
    
    The NBD spec recommends (but not requires) that ENOTSUP be avoided for
    all but failures of a fast zero (the only time it is mandatory to
    avoid an ENOTSUP failure is when fast zero is supported but not
    requested during write zeroes; the questionable use is for ENOTSUP to
    other actions like a normal write request).  However, clients that get
    an unexpected ENOTSUP will either already be treating it the same as
    EINVAL, or may appreciate the extra bit of information.  We were
    equally loose for returning EOVERFLOW in more situations than
    recommended by the spec, so if it turns out to be a problem in
    practice, a later patch can tighten handling for both error codes.
    
    Signed-off-by: Eric Blake <eblake@redhat.com>
    Message-Id: <20190823143726.27062-3-eblake@redhat.com>
    Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
    [eblake: tweak commit message, also handle EOPNOTSUPP]
  4. nbd: Improve per-export flag handling in server

    ebblake committed Aug 23, 2019
    When creating a read-only image, we are still advertising support for
    TRIM and WRITE_ZEROES to the client, even though the client should not
    be issuing those commands.  But seeing this requires looking across
    multiple functions:
    
    All callers to nbd_export_new() passed a single flag based solely on
    whether the export allows writes.  Later, we then pass a constant set
    of flags to nbd_negotiate_options() (namely, the set of flags which we
    always support, at least for writable images), which is then further
    dynamically modified with NBD_FLAG_SEND_DF based on client requests
    for structured options.  Finally, when processing NBD_OPT_EXPORT_NAME
    or NBD_OPT_EXPORT_GO we bitwise-or the original caller's flag with the
    runtime set of flags we've built up over several functions.
    
    Let's refactor things to instead compute a baseline of flags as soon
    as possible which gets shared between multiple clients, in
    nbd_export_new(), and changing the signature for the callers to pass
    in a simpler bool rather than having to figure out flags.  We can then
    get rid of the 'myflags' parameter to various functions, and instead
    refer to client for everything we need (we still have to perform a
    bitwise-OR for NBD_FLAG_SEND_DF during NBD_OPT_EXPORT_NAME and
    NBD_OPT_EXPORT_GO, but it's easier to see what is being computed).
    This lets us quit advertising senseless flags for read-only images, as
    well as making the next patch for exposing FAST_ZERO support easier to
    write.
    
    Signed-off-by: Eric Blake <eblake@redhat.com>
    Message-Id: <20190823143726.27062-2-eblake@redhat.com>
    Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
    [eblake: improve commit message, update iotest 223]
  5. docs: Update preferred NBD device syntax

    ebblake committed Sep 3, 2019
    Mention the preferred URI form, especially since NBD is trying to
    standardize that form: https://lists.debian.org/nbd/2019/06/msg00012.html
    
    Signed-off-by: Eric Blake <eblake@redhat.com>
    Message-Id: <20190903145634.20237-1-eblake@redhat.com>
    Reviewed-by: John Snow <jsnow@redhat.com>
  6. block: workaround for unaligned byte range in fallocate()

    Andrey Shinkevich authored and ebblake committed Aug 27, 2019
    Revert the commit 118f994 'block/io.c: fix for the allocation failure'
    and use better error handling for file systems that do not support
    fallocate() for an unaligned byte range. Allow falling back to pwrite
    in case fallocate() returns EINVAL.
    
    Suggested-by: Kevin Wolf <kwolf@redhat.com>
    Suggested-by: Eric Blake <eblake@redhat.com>
    Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
    Reviewed-by: Eric Blake <eblake@redhat.com>
    Reviewed-by: Denis V. Lunev <den@openvz.org>
    Message-Id: <1566913973-15490-1-git-send-email-andrey.shinkevich@virtuozzo.com>
    Signed-off-by: Eric Blake <eblake@redhat.com>
  7. nbd: Tolerate more errors to structured reply request

    ebblake committed Aug 24, 2019
    A server may have a reason to reject a request for structured replies,
    beyond just not recognizing them as a valid request; similarly, it may
    have a reason for rejecting a request for a meta context.  It doesn't
    hurt us to continue talking to such a server; otherwise 'qemu-nbd
    --list' of such a server fails to display all available details about
    the export.
    
    Encountered when temporarily tweaking nbdkit to reply with
    NBD_REP_ERR_POLICY.  Present since structured reply support was first
    added (commit d795299 reused starttls handling, but starttls is
    different in that we can't fall back to other behavior on any error).
    
    Note that for an unencrypted client trying to connect to a server that
    requires encryption, this defers the point of failure to when we
    finally execute a strict command (such as NBD_OPT_GO or NBD_OPT_LIST),
    now that the intermediate NBD_OPT_STRUCTURED_REPLY does not diagnose
    NBD_REP_ERR_TLS_REQD as fatal; but as the protocol eventually gets us
    to a command where we can't continue onwards, the changed error
    message doesn't cause any security concerns.
    
    Signed-off-by: Eric Blake <eblake@redhat.com>
    Message-Id: <20190824172813.29720-3-eblake@redhat.com>
    Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
    [eblake: fix iotest 233]
  8. nbd: Use g_autofree in a few places

    ebblake committed Aug 24, 2019
    Thanks to our recent move to use glib's g_autofree, I can join the
    bandwagon.  Getting rid of gotos is fun ;)
    
    There are probably more places where we could register cleanup
    functions and get rid of more gotos; this patch just focuses on the
    labels that existed merely to call g_free.
    
    Signed-off-by: Eric Blake <eblake@redhat.com>
    Message-Id: <20190824172813.29720-2-eblake@redhat.com>
    Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
    Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
  9. nbd: Advertise multi-conn for shared read-only connections

    ebblake committed Aug 15, 2019
    The NBD specification defines NBD_FLAG_CAN_MULTI_CONN, which can be
    advertised when the server promises cache consistency between
    simultaneous clients (basically, rules that determine what FUA and
    flush from one client are able to guarantee for reads from another
    client).  When we don't permit simultaneous clients (such as qemu-nbd
    without -e), the bit makes no sense; and for writable images, we
    probably have a lot more work before we can declare that actions from
    one client are cache-consistent with actions from another.  But for
    read-only images, where flush isn't changing any data, we might as
    well advertise multi-conn support.  What's more, advertisement of the
    bit makes it easier for clients to determine if 'qemu-nbd -e' was in
    use, where a second connection will succeed rather than hang until the
    first client goes away.
    
    This patch affects qemu as server in advertising the bit.  We may want
    to consider patches to qemu as client to attempt parallel connections
    for higher throughput by spreading the load over those connections
    when a server advertises multi-conn, but for now sticking to one
    connection per nbd:// BDS is okay.
    
    See also: https://bugzilla.redhat.com/1708300
    Signed-off-by: Eric Blake <eblake@redhat.com>
    Message-Id: <20190815185024.7010-1-eblake@redhat.com>
    [eblake: tweak blockdev-nbd.c to not request shared when writable,
    fix iotest 233]
    Reviewed-by: John Snow <jsnow@redhat.com>
  10. Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2…

    pm215 committed Sep 5, 2019
    …019-09-05-v2' into staging
    
    - Make the core libqtest library independent from global_qtest
    - Clean up docs from hard-coded qemu-system-* names
    - Install libattr-dev and libcap-dev in gitlab-ci to test virtio-9p
    
    # gpg: Signature made Thu 05 Sep 2019 15:52:30 BST
    # gpg:                using RSA key 27B88847EEE0250118F3EAB92ED9D774FE702DB5
    # gpg:                issuer "thuth@redhat.com"
    # gpg: Good signature from "Thomas Huth <th.huth@gmx.de>" [full]
    # gpg:                 aka "Thomas Huth <thuth@redhat.com>" [full]
    # gpg:                 aka "Thomas Huth <huth@tuxfamily.org>" [full]
    # gpg:                 aka "Thomas Huth <th.huth@posteo.de>" [unknown]
    # Primary key fingerprint: 27B8 8847 EEE0 2501 18F3  EAB9 2ED9 D774 FE70 2DB5
    
    * remotes/huth-gitlab/tags/pull-request-2019-09-05-v2:
      gitlab-ci.yml: Install libattr-devel and libcap-devel to test virtio-9p
      qemu-doc: Do not hard-code the name of the QEMU binary
      tests/vm: Take the J=x setting into account for the vm-boot-ssh targets, too
      tests/libqtest: Use libqtest-single.h in tests that require global_qtest
      tests/libqtest: Move global_test wrapper function into a separate header
      tests: Remove unnecessary global_qtest references
      tests/libqos: Replace clock_step with qtest_clock_step in virtio code
      tests/libqos/e1000e: Make e1000e libqos functions independent from global_qtest
      tests/migration: Do not use functions anymore that rely on global_qtest
    
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
  11. Merge remote-tracking branch 'remotes/berrange/tags/docs-pull-request…

    pm215 committed Sep 5, 2019
    …' into staging
    
    docs: add docs about use of automatic cleanup functions
    
    This is ostensibly about adding docs for the g_autofree/g_autoptr
    macros. As part of doing that, however, the existing HACKING doc
    is merged into the CODING_STYLE doc and the text is converted to
    rst with a table of contents.
    
    # gpg: Signature made Thu 05 Sep 2019 14:43:44 BST
    # gpg:                using RSA key DAF3A6FDB26B62912D0E8E3FBE86EBB415104FDF
    # gpg: Good signature from "Daniel P. Berrange <dan@berrange.com>" [full]
    # gpg:                 aka "Daniel P. Berrange <berrange@redhat.com>" [full]
    # Primary key fingerprint: DAF3 A6FD B26B 6291 2D0E  8E3F BE86 EBB4 1510 4FDF
    
    * remotes/berrange/tags/docs-pull-request:
      docs: split the CODING_STYLE doc into distinct groups
      docs: document use of automatic cleanup functions in glib
      docs: merge HACKING.rst contents into CODING_STYLE.rst
      docs: convert README, CODING_STYLE and HACKING to RST syntax
    
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
  12. gitlab-ci.yml: Install libattr-devel and libcap-devel to test virtio-9p

    huth committed Sep 5, 2019
    So far the gitlab-ci was not testing virtio-9p yet, since we did not
    install libattr-devel and libcap-devel in any of the pipelines. Do
    it now to get some more test coverage.
    
    Message-Id: <20190905111729.1197-1-thuth@redhat.com>
    Acked-by: Greg Kurz <groug@kaod.org>
    Signed-off-by: Thomas Huth <thuth@redhat.com>
  13. docs: split the CODING_STYLE doc into distinct groups

    berrange committed Aug 29, 2019
    Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
    Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
  14. docs: document use of automatic cleanup functions in glib

    berrange committed Aug 23, 2019
    Document the use of g_autofree and g_autoptr in glib for automatic
    freeing of memory.
    
    Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
    Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
  15. docs: merge HACKING.rst contents into CODING_STYLE.rst

    berrange committed Aug 23, 2019
    The split of information between the two docs is rather arbitary and
    unclear. It is simpler for contributors if all the information is in
    one file.
    
    Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
    Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
  16. docs: convert README, CODING_STYLE and HACKING to RST syntax

    berrange committed Aug 23, 2019
    Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
    Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
  17. target/arm: Inline gen_bx_im into callers

    rth7680 authored and pm215 committed Sep 4, 2019
    There are only two remaining uses of gen_bx_im.  In each case, we
    know the destination mode -- not changing in the case of gen_jmp
    or changing in the case of trans_BLX_i.  Use this to simplify the
    surrounding code.
    
    For trans_BLX_i, use gen_jmp for the actual branch.  For gen_jmp,
    use gen_set_pc_im to set up the single-step.
    
    Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
    Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
    Message-id: 20190904193059.26202-70-richard.henderson@linaro.org
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
  18. target/arm: Clean up disas_thumb_insn

    rth7680 authored and pm215 committed Sep 4, 2019
    Now that everything is converted, remove the rest of
    the legacy decode.
    
    Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
    Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
    Message-id: 20190904193059.26202-69-richard.henderson@linaro.org
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
  19. target/arm: Convert T16, long branches

    rth7680 authored and pm215 committed Sep 4, 2019
    Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
    Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
    Message-id: 20190904193059.26202-68-richard.henderson@linaro.org
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
  20. target/arm: Convert T16, Unconditional branch

    rth7680 authored and pm215 committed Sep 4, 2019
    Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
    Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
    Message-id: 20190904193059.26202-67-richard.henderson@linaro.org
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
  21. target/arm: Convert T16, load (literal)

    rth7680 authored and pm215 committed Sep 4, 2019
    Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
    Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
    Message-id: 20190904193059.26202-66-richard.henderson@linaro.org
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
  22. target/arm: Convert T16, shift immediate

    rth7680 authored and pm215 committed Sep 4, 2019
    Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
    Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
    Message-id: 20190904193059.26202-65-richard.henderson@linaro.org
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
  23. target/arm: Convert T16, Miscellaneous 16-bit instructions

    rth7680 authored and pm215 committed Sep 4, 2019
    Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
    Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
    Message-id: 20190904193059.26202-64-richard.henderson@linaro.org
    Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Older
You can’t perform that action at this time.