cachepc-qemu

Fork of AMDESE/qemu with changes for cachepc side-channel attack
git clone https://git.sinitax.com/sinitax/cachepc-qemu
Log | Files | Refs | Submodules | LICENSE | sfeed.txt

BSD-3-Clause (1845B)


      1Valid-License-Identifier: BSD-3-Clause
      2SPDX-URL: https://spdx.org/licenses/BSD-3-Clause.html
      3Usage-Guide:
      4  To use the BSD 3-clause "New" or "Revised" License put the following SPDX
      5  tag/value pair into a comment according to the placement guidelines in
      6  the licensing rules documentation:
      7    SPDX-License-Identifier: BSD-3-Clause
      8License-Text:
      9
     10Copyright (c) <year> <owner> . All rights reserved.
     11
     12Redistribution and use in source and binary forms, with or without
     13modification, are permitted provided that the following conditions are met:
     14
     151. Redistributions of source code must retain the above copyright notice,
     16   this list of conditions and the following disclaimer.
     17
     182. Redistributions in binary form must reproduce the above copyright
     19   notice, this list of conditions and the following disclaimer in the
     20   documentation and/or other materials provided with the distribution.
     21
     223. Neither the name of the copyright holder nor the names of its
     23   contributors may be used to endorse or promote products derived from this
     24   software without specific prior written permission.
     25
     26THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
     27AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
     28IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
     29ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
     30LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
     31CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
     32SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
     33INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
     34CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
     35ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
     36POSSIBILITY OF SUCH DAMAGE.